Repository navigation
FontSizePicker incorrectly measures units for selecting elements #71967
Description
Description
I see that WordPress show incorrect information of units of FontSizePicker if user choose default to the labels 'S / M / L / XL / XXL'.
Example my component
<FontSizePicker
__next40pxDefaultSize
fontSizes={ [
{
name: 'Small',
size: 12,
slug: 'small',
},
{
name: 'Normal',
size: 16,
slug: 'normal',
},
{
name: 'Big',
size: 26,
slug: 'big',
},
] }
value={ titleFontSize ? parseFloat( titleFontSize ) : undefined }
onChange={ ( newSize ) => {
if ( newSize === undefined ) {
setAttributes( {
titleFontSize: '16',
titleFontUnit: 'px',
} );
return;
}
setAttributes( {
titleFontSize: String( newSize ),
titleFontUnit: 'px',
} );
} }
withSlider
/>;Step-by-step reproduction instructions
I created a simple plugin to see the problem
Screenshots, screen recording, code snippet
I saw this. ->
This component does not correctly indicate the units of measurement when switching between different states. Ideally it should show the font size in "px" but in fact it displays the value in "rem", but writes that it is "px"
Environment info
I use WordPress Version 6.8.2 with current Gutenberg
Please confirm that you have searched existing issues in the repo.
- Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
- Yes
Please confirm which theme type you used for testing.
- Block
- Classic
- Hybrid (e.g. classic with theme.json)
- Not sure
Activity
CharlesAustin commentedon Oct 15, 2025
Took a quick look and wasn't able to reproduce this, do you have a link to a git repository as opposed to a zip file for more in-depth testing?
BlackStar1991 commentedon Oct 22, 2025
@CharlesAustin https://github.com/BlackStar1991/Test-FontSizePicker simple test plugin
github-actions commentedon Nov 22, 2025
Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.
SirLouen commentedon Dec 10, 2025
Reproduction Report
Description
✅ This report can validate that the issue can be reproduced.
Environment
Testing Instructions
https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fgist.githubusercontent.com%2FSirLouen%2Fad20b27776227c6a53b418a44b564817%2Fraw%2Fe5b5d0b828980041584f1f01416125353f4cb146%2Fgistfile1.txt&php=8.3&wp=trunk&networking=yes&language=&multisite=no&random=47puqlcay9y
Raw blueprint: https://gist.githubusercontent.com/SirLouen/ad20b27776227c6a53b418a44b564817/raw/e5b5d0b828980041584f1f01416125353f4cb146/gistfile1.txt
TestblockUse size presetbuttonSet custom sizebuttonActual Results
Additional Notes
BlackStar1991 commentedon Dec 10, 2025
@SirLouen Please try again
Windows 10 Wordpress 6.9 Chrome 147
SirLouen commentedon Dec 10, 2025
Are you using the playground link I put? Which browser are you using?
Oh wait I think I can reproduce it, I will give it a second go later
SirLouen commentedon Dec 11, 2025
I've been able to reproduce it with your conditions, and I've updated the instructions for the reproduction report so now it's very easy to follow
Be aware that I'm not 100% confident that the plugin provided is working as it should, and if this is or isn't the expected behavior. All I've done is testing with the provided instructions. I have not dug further into the
font-size-pickercomponent and I'm not sure if this should be extended in your plugin to cover your use case, or if it's actually a bug, or an enhancement.I'm going to switch the Type to Discussion, I would like to have someone more versed in this component that I am comment with a better opinion. If it can be confirmed, that this is actually a bug, I will switch it back to Bug.
cc @luminuu
sarthaknagoshe2002 commentedon Jul 2, 2026
I have investigated this and tested it using multiple plugins and multiple ways. I am unable to reproduce the issue; the FontSizePicker component appears to be working fine natively on my end.