Make WordPress Core

Opened 4 days ago

Last modified 4 days ago

#63182 new defect (bug)

Issues with Color & Typography Settings

Reported by: ketanniruke's profile ketanniruke Owned by:
Milestone: 6.8 Priority: normal
Severity: normal Version: trunk
Component: Editor Keywords: close
Focuses: ui Cc:

Description

While testing the features in WordPress 6.8 RC1, I identified the following issues related to typography settings in the post editor:

1. Typography Size Display & Unit Conversion Issue

  • By default, typography size options appear as S, M, L, XL, etc.
  • When customizing the size, it initially displays values in rem.
  • If I switch to px (pixels), the rem value should be converted accordingly, but it still displays the rem value alongside px, causing inconsistency.

These issues were observed while thoroughly testing all features.

Change History (5)

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


4 days ago

#2 @audrasjbCore Committer
4 days ago

  • Component changed from General to Editor
  • Milestone changed from Awaiting Review to 6.8
  • Type changed from enhancement to defect (bug)
  • Version set to trunk

Hello and thanks you for reporting this issue,

I'm moving this ticket to milestone 6.8 for now but I'm not sure this was introduced in 6.8.

Could you please check whether the issue can also be reproduced 6.7.2? Thank you.

Pinging @Mamaduka as 6.8 Editor Tech Lead.

#3 @MamadukaCore Committer
4 days ago

The editor's unit controls rarely support value conversion on unit change, so this isn't a regression or a bug.

The main reason for avoiding conversion is that it's challenging to do correctly. Let's take a simple example: PX to REM. The standard formula is pxValue / 16 = REMValue. Here, we already had to assume that the root size is 16, which can be incorrect based on user setup.

It gets more challenging when you consider fixed to relative value conversions. How do you convert 100px into a percentage when the code doesn't know what % is referring to?

#4 @audrasjbCore Committer
4 days ago

  • Keywords close added; needs-patch removed

Thanks for the detailed feedback. Indeed, it doesn't look like something that can be addressed in 6.8, and it may be a wontfix.
Adding close keyword for now.

#5 @audrasjbCore Committer
4 days ago

  • Focuses tests removed
Note: See TracTickets for help on using tickets.