-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove font size classes that are enqueued in the global stylesheet #35182
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasmussen I've noticed that in the
common.scss
bundled the classes usedem
while in theeditor.scss
bundled they usedpx
. Looked at the history but this seems to be like that since the beggining. Do you happen to remember why that difference by any chance? Is it safe to substitute them with thetheme.json
values inpx
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. There's a lot of discussion around ems vs. px, but since we have a unit selector in the interface, px provides a default that's fairly easy to understand in comparison.
So why are the values in px in the editor and em in the interface? Good question, that seems like an oversight.
Is it safe to remove? Almost certainly. Looking at the values, we have 0.8125em for "small", which maps to 13px in theme.json. The math checks out because ems are based on the parent font size, which in the case of the body element is 16px by default. And 0.8125 * 16 = 13.
Two issues:
But in both cases, it appears those issues are in trunk and already shipping, meaning all this PR does is correct an error. It also appears that the global styles that are output have already corrected this error, meaning this is just code cleanup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, since we load the global stylesheet for all themes, the core classes enqueued there are overriding these styles already.