-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix: font size syncing #142
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,13 @@ | ||
export function hostSyncFont(host) { | ||
host.onRequest('font', () => { | ||
const computedStyle = window.getComputedStyle(document.body); | ||
const bodyComputedStyle = window.getComputedStyle(document.body); | ||
const rootComputedStyle = window.getComputedStyle(document.documentElement); | ||
const visualRedesign = document.body.classList.contains('visual-redesign'); | ||
|
||
return { | ||
family: computedStyle.fontFamily, | ||
size: computedStyle.fontSize, | ||
visualRedesign: visualRedesign | ||
family: bodyComputedStyle.fontFamily, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still using body to grab the font family. Isn't used but have it for compatibility. |
||
size: rootComputedStyle.fontSize, | ||
visualRedesign | ||
}; | ||
}); | ||
} |
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.
To me, this seems like the bug right here? Like in our LMS pages, we output this:
And that value changes when the user changes their font size preference in account settings. So could we just always grab it from the root and always set it on the root and ignore the body completely?
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.
Yeah, this is what started the font syncing discussion. In Portfolio we want to reflect the font size preference inside our iFrame.
We weren't sure if others depend on the current behaviour (getting computed style from
<body>
rather than<html>
).If it makes sense that the style comes right from
<html>
(and it doesn't break existing usage), then it might be cleanest to always get the computed style from the rootThere 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.
I'm ok with treating this as a bug. I'm less worried after thinking about the fact that teams have to upgrade to get the new version of
ifrau
anyways and would hopefully test and see the difference. I can make the adjust to just grab thehtml
font size and not introduce the newsizeRoot
stuff if that works for everyone.