Represent default font size in slider

[mtias]

Now that we have more concrete mechanisms for knowing what is the default font size coming for text from the global styles tree, can we represent it on the segmented control if it matches one of the preset sizes?

I'd imagine we would use a lighter gray for these cases.

[jasmussen]

Here are a few options including a lighter gray:

Another option is to show a little asterisk or other indicator:

Or a combination?

None of these seem a clear win, though I'd tend to agree the light gray background is probably best out of these.

[jameskoster]

Isn't the label alone adequate? It seems more important for the default size to be selected when the control is present?

[jasmussen]

Oh interesting, I read the brief as when no font size is set, suggest which point on the slider it would match. 🤔

[jameskoster]

If no font size is set (it is inherited from css), then we can't determine which value it would match? 🤔

I saw this as more about connecting the setting in global styles to the control we find when editing locally. Apologies if that's separate.

[jasmussen]

The font size can be set in Global Styles, in which case we would know whether it matched a given notch in the slider.

[jameskoster]

We should. But it hasn't been implemented here. I think that's the issue?

As an example, here's my font size setting from the Typography section of global styles:

But when I go to edit the Paragraph block in global styles, or just select a paragraph while editing a post, here's what I see:

The label tells me the default size is set, but the corresponding segment (M) isn't highlighted.

[jasmussen]

Right, that's the baseline, and works okay, I think the question is whether we need more than that.

[jameskoster]

Indeed, and my suggestion was that if the correct value is highlighted in the control, isn't the label denoting the default adequate? So if I select a paragraph in a post, I see this in the Typography panel:

[mtias]

Selecting M explicitly for a paragraph is not the same as M being the inherited default when nothing is locally set but M is the most immediate value passed in the tree.

[jameskoster]

I believe #49278 captures this in a more holistic way. All controls need a solution to this problem.