Conversation
…an Editor's Draft Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
1aadd10
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fb6cd670.specification-website.pages.dev |
| Branch Preview URL: | https://considered-meta-text-scale-2.specification-website.pages.dev |
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.
What changed
Adds
src/content/considered/meta-text-scale.md— atoo-earlyentry in the/considered/register for<meta name="text-scale">.No spec page. This is the "found something real but premature" output.
Why now
Turned up by the daily standards scan while resolving MDN citations for the rotating slice. It is genuinely new to us and nothing in
src/content/spec/orsrc/content/considered/mentions it.<meta name="text-scale" content="scale">opts a page in to having the root element's initialfont-sizescale with OS and browser text-size settings, disables the browser's own text-autosizing heuristics, and populatesenv(preferred-text-scale)on desktop. It is the right shape for a spec page: one element in the<head>, auditable from outside, with a visitor-facing outcome rather than a developer-convenience one.Why it does not get a page yet
experimental: true.content="scale"must be tested to 200–300%+ scaling. The honest page would mostly be advice about sizing in relative units, which the viewport meta page already reaches from the pinch-zoom side.Revisit condition
A second engine shipping it and the section leaving the Editor's Draft. Deliberately both, not either — a stable definition nobody else implements is still a one-browser recommendation, and a second implementation of an unstable definition can be obsoleted by the next editorial pass.
Sources
text-scale-meta(W3C CSS WG, Editor's Draft)<meta name="text-scale">(resolved via the MDN MCP server, incl. BCD)Checks
npm run buildpasses (170 pages),npm run lintandnpm run format:checkclean, pre-commitcheck:skillgreen (page count unchanged —/considered/is not part of the spec collection). No changelog entry: the changelog is about what the spec says, and this adds no spec page.🤖 Generated with Claude Code