Option in theme.json to (completely) disable typography controls on block level

[lunule]

What problem does this address?

Typography controls configuration in theme.json doesn't work properly.

The example I tested is the fontSizes setting, with the following scenario:

• I have font sizes configured on global level (in the settings section)
• most of the blocks should have typography controls, but not the core/heading block where I want fix font sizes
  • that can't be changed by the user
  • that are not available in the array of font sizes mentioned above
• as a result, I need to disable the font size selector for the core/heading block only - but this is currently impossible.

I tested the following variations:

• "fontSize: false"
• "fontSizes: false"
• "fontSize: []"
• "fontSizes: []"

... in all possible combos, and by applying these combos

• in the styles section for the core/heading block
• in the elements section for the h1 element

None of these variations work, it seems that, currently, it's impossible to disable the font size selector on block level if/when the fontSizes array in the settings section is not an empty array (or if it's not set to false).

What is your proposed solution?

The proposed solution is an option in theme.json to completely disable typography controls on block level.

[carolinan]

Hi
I may be misunderstanding something; did you set it to false under styles.blocks.core/heading? Not under settings.blocks.core/heading?
Styles is used to apply default styles, not to change the available options.

This combination works for me in my test:
Under settings:

		"blocks": {
			"core/heading": {
				"typography": {
					"fontSizes": [],
					"customFontSize": false
				}
			}
		}

I see that the font size is still available as a menu item when I open the "Typography options" from the three dot menu in the block's typography panel, even though the control itself never shows. That does seem like a bug.

[carolinan]

I tested one more thing, for your use case, you probably also want to turn off the font size for the heading elements.
I found that elements is not valid under settings, and I did not find a way to turn the font size off.

It may be a non-issue for scenarios where you are using a classic theme, or you are using a block theme and you want an administrator to have access but not editors. But it would be good to be able to completely disable it.

[lunule]

Hey @carolinan - thanks for taking a look into this.

did you set it to false under styles.blocks.core/heading? Not under settings.blocks.core/heading?

You're right, and I learned something today. I have, indeed, tested it in styles.blocks.core/heading.
I just checked the settings.blocks.core/heading version, and it works - yay!!

But this is is a quiet 'yay', because we still have

• the issue that the control can't be disabled by header level, e.g. I might need to enable it for h2s and disable it for h3s, this is still not possible (I just realized that this is the what you describe in your second comment);
• the bug, with the 'Font Sizes' menu item still being displayed in the Typography dropdown.

---

(...) But it would be good to be able to completely disable it.

👍I couldn't agree more.

[t-hamano]

the issue that the control can't be disabled by header level, e.g. I might need to enable it for "h2"s and disable it for "h3"s, this is still not possible (I just realized that this is the what you describe in your second comment);

Can't this be achieved with blockEditor.useSetting.before hook? Coincidentally, the Developer Blog has a code example that changes settings depending on the heading level.

Curating the Editor experience with client-side filters – WordPress Developer Blog

See "Restricting settings by block attributes" section

[carolinan]

Thank you for sharing the article.
It is quiet a big gap between these filters and adding a value to theme.json

[lunule]

Hey @t-hamano , thanks for this share - awesome article, and, actually, the availability of this filter is a solution of the issue described in this feature request.

@carolinan , I need your opinion here 🙂 - while I can use the blockEditor.useSetting.before filter to disable typo controls for specific heading levels, I also agree with your statement ("It is quiet a big gap between these filters and adding a value to theme.json").

What do you think, does the solution described in the artice mean this ticket is to be closed - or let's keep it open with the hope that, one day, support for the requested feature will be added to the theme.json file?

[t-hamano]

Personally, I think it would be better to close this issue and submit the following two issues:

• Bug report: The menu appears in the Typography panel even if you completely disable font size at the block level. This may be a problem with other settings as well as font size.
• Feature request: Allows control of block support depending on heading level via theme.json. I think this means that block support is controlled by the value of the block's attributes.

[carolinan]

Yes, I have opened a separate issue for the first: #59732