Specify explicit fonts to fix issue on MacOS Tahoe - #1838
Merged
Conversation
bcotrim
approved these changes
Oct 2, 2025
bcotrim
left a comment
bcotrim
left a comment
Contributor
There was a problem hiding this comment.
LGTM 👍
But I couldn't replicate the original issue.
Running the updated version works without any regression.
Contributor
|
I also tested on Windows and I can see the emojis as expected in both |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Related issues
Proposed Changes
This update extends the default font-family stack to include emoji and Unicode-friendly fonts. Previously, Hebrew, emoji, and other non-Latin characters rendered as missing glyphs (tofu boxes) due to stricter fallback handling in macOS Tahoe.
With this change, Studio will:
Testing Instructions
Pre-merge Checklist