docs(README): caveat that the icon_names subset can render axes differently than the full font - #2006
Open
AKnassa wants to merge 1 commit into
Open
docs(README): caveat that the icon_names subset can render axes differently than the full font#2006AKnassa wants to merge 1 commit into
AKnassa wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Adds a short caveat to the Material Symbols section of the README documenting that Google Fonts' server-side `icon_names` subset can render glyphs at a different stroke/fill/weight state than the full, un-subset font, regardless of the requested `font-variation-settings`. Only the subset (fonts.gstatic.com/l/font?kit=...) is affected; the full font (fonts.gstatic.com/s/...) renders correctly. Documents two working workarounds (drop icon_names, or self-host the shipped variablefont/ woff2) and notes this is a Google Fonts serving behavior that a PR to this repo cannot itself change. Docs-only; no icon or script files touched. Reported in google#1997. Related open reports: google#1834, google#1818. Claude-Session: https://claude.ai/code/session_01VY8qBKMt6C2B7iPBopiwni
AKnassa
force-pushed
the
docs/icon-names-subset-caveat
branch
from
July 11, 2026 00:25
c909031 to
c5e9422
Compare
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
1 participant
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.
This adds a short caveat to the Material Symbols section of the README.
What's the problem? When you use Google Fonts'
icon_namesfeature to load only the icons you need, the trimmed-down font it sends back can draw icons at a different stroke, fill, or weight than the full font — even when your CSS asks for the same settings. It mainly shows up with large icon lists, and because Google generates that trimmed font on their servers, an app can suddenly start rendering wrong without anyone touching the app's own code (build steps that inline Google Fonts CSS can even freeze the broken version into a release).What does this change? Nothing in the icons or the scripts — this is documentation only. The new note explains the behavior, points out that only the trimmed (subset) font is affected while the full font renders fine, and gives two things a developer can do today: stop passing the
icon_namesparameter, or self-host the full variable font that already ships in this repo.Why here? This is the repository developers land on when they hit this, and the reporter specifically asked for a documented note as an acceptable resolution. The wording is careful to say this is a Google Fonts serving behavior, not something a pull request to this repo can fix, so it stays consistent with the project's "no pull requests for icon files" policy.
Reported in #1997. Related open reports: #1834 and #1818.