#1208: Other Spec Review: [css-text] `text-fit` property

Visit on Github

Opened Mar 23, 2026

Specification

https://github.com/w3c/csswg-drafts/pull/13616

Explainer

https://github.com/explainers-by-googlers/css-fit-text/blob/main/README.md

Links

  • Previous early design review, if any: None
  • An introduction to the feature, aimed at unfamiliar audiences: See the explainer <!-- Can be the specification's or explainer's introduction, or another section. -->
  • A description of the problems that end-users were facing before this proposal: See the explainer <!-- See https://w3ctag.github.io/explainer-explainer/#end-user-need -->
  • Alternatives considered: See the explainer <!-- See https://w3ctag.github.io/explainer-explainer/#alternatives -->
  • Examples of how to use the proposal to solve the end-users' problems: See the explainer <!-- See https://w3ctag.github.io/explainer-explainer/#describe-proposal -->
  • What do the end-users experience with this proposal: https:// <!-- See https://w3ctag.github.io/explainer-explainer/#describe-proposal -->
  • User research you did to validate the problem and/or design, if any: No public one.
  • Web Platform Tests: Not merged yet. Tests in Chromium repo <!-- Or other tests if this is not a web platform feature. -->

The specification

Where and by whom is the work is being done?

  • GitHub repo: https://github.com/w3c/csswg-drafts
  • Primary contacts:
    • @tkent-google, Google, Specification writer / Implementer in Chromium
    • @kizu, DataDog, Proposer
    • <!-- repeat as necessary, we recommend including group chairs and editors in this list -->
  • Organization/project driving the specification: Google
  • This work is being funded by:
  • Primary standards group developing this feature: CSSWG
  • Group intended to standardize this work: <!-- if different from the current group -->
  • Incubation and standards groups that have discussed the design:

Feedback so far

You should also know that...

No response

<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1208

Discussions

Log in to see TAG-private discussions.

Discussed Apr 6, 2026 (See Github)

Matthew: This is interesting. Assigned myself to this during triage, seems nobody else assigned. This is new, haven’t looked at it yet. Will have a look early next week.

Discussed Apr 20, 2026 (See Github)

Matthew: Already looked at this in APA. There are several interesting discussions going in within the CSS WG regarding what the limits of this should be. Combining this with a screen magnifier may also render it too big. Know that they have a similar discussion about the <meta> text-scale feature. APA is working with them. Try to put together a TAG comment as soon as possible. There's a lot of caveats to consider.

Discussed Apr 27, 2026 (See Github)

Matthew: I proposed a draft comment. This is about changing the height of a font so that the text is more justified in the container that it’s in, to make sure lines start and end properly. I have some concerns about edge cases. There is cross-engine commitment. Jeffrey put up a comment that seems to be in agreement with my points.

Ehsan: Had a brief look, but didn’t see any privacy section for this. Skimming through the explainer, I believe it can have potential for fingerprinting, given it’s adaptive to various screen sizes. Would love to see their point on this.

Matthew: Agree that’s worth asking.

Lola: They have an issue about a11y open, and it’s still open. What are your thoughts?

Matthew: Largely good, they have done serious work on it.

Lola: So you would draft a comment related to WCAG, baseline mechanics, …?

Matthew: Yes.

Ehsan: Happy to help.