[Possible Bug] Icon size and letter-spacing responsive values

That’s strange – any chance you can link me to an example so I can take a closer look?

Let me know ??

Very easy to replicate:

1. Create a heading and set a custom letter spacing/font size value or leave empty for Customizer defaults.
2. Switch to Tablet/Mobile.
3. If font size desktop value was empty, font size is displayed as 17, otherwise it shows the value from the desktop.
4. Line spacing values always shows 0.01 whatever the value is entered in the desktop settings.

Keep in mind that the previous shown responsive values do not actually affect the outcome. Sizes keep their sizes fine. It’s just the feedback you get is confusing.

Hi,

I’m not sure what you mean by “Line spacing”. Perhaps you meant “Letter spacing”?

If so, I’ve tried replicating the issue and I didn’t encounter what was mentioned on #4 as shown here:
https://share.getcloudapp.com/YEuXgG70

As you can see in the video. I’ve entered different values on different viewports and they reflect on the live preview. They’ve also been retained to the live version of the site.

I’m using GB’s latest version. (1.3.1)

Yes, I meant letter-spacing.

At 0.54, when you switch to Tablet, the font value shows as 20 even though you set 50 on desktop. Also, letter-spacing shows 0.5 as a default value even though you set it at 1.5 on desktop.

At 0.49, font-size shows at 14 for Tablet even though it is set as 50 on desktop. Letter-spacing shows as 0.01 even though it is set at 1.5 on desktop.

At 0.35, letter-spacing is 0.5 for Tablet even though you just set it as 2 for desktop. Then you set it at 1 for Tablet, you head to Mobile and it shows 0.01 again!

I am not saying it’s not displaying fine on the front-end, it’s just the values are inconsistent.

Ah, the placeholders in the editor.

The 0.01 is just an example in this case, as we can’t get the actual value from the theme.

However, you’re right that it should update on tablet/mobile depending on your values. Right now it’s always 0.01, which can definitely be confusing.

Will get this fixed in 1.4.0.

Thanks!

Nice one, thanks, Tom!

No problem – thanks again for the heads up ??