I’m excited to see this prototype, but please take a look at the accessibility concerns raised in the issue you link to. I’d like to see the explainer work through these concerns and propose ways to address them.
On Thursday, April 24, 2025 at 1:32:01 AM UTC-7 tk...@chromium.org wrote: > Contact emailstk...@chromium.org, ikilp...@chromium.org, > ko...@chromium.org > > Explainer > https://github.com/explainers-by-googlers/css-fit-text/blob/main/README.md > > SpecificationNone > > Summary > > This new CSS capability empowers web developers to precisely fit lines of > text to the exact width of their containing element. Unlike traditional > justification methods that adjust spacing, this feature dynamically scales > the font-size itself, ensuring text lines seamlessly align with both the > left and right edges of the container. Web developers often need to ensure > text content, especially headings or short phrases, fully utilizes the > available container width without causing overflow or appearing too narrow. > This feature addresses this by intelligently adjusting the font-size of the > text. It's particularly useful in responsive designs or when dealing with > dynamic content, such as text from translations that might be unexpectedly > long, or user-generated input where word length is unpredictable. If a word > or line of text would normally overflow its container, these CSS properties > will reduce the font-size to make it fit. Conversely, if the text is > narrower than the container, the font-size can be increased to fill the > space, providing a visually balanced and "justified" appearance through > size scaling rather than space distribution. > > > Blink componentBlink>Layout>Inline > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ELayout%3EInline%22> > > Motivation > > None > > > Initial public proposalNone > > TAG reviewNone; Will request later. > > TAG review statusPending > > Risks > > > Interoperability and Compatibility > > None > > > *Gecko*: No signal; Will file a standard-position issue. > > *WebKit*: No signal; Will file a standard-position issue. > > *Web developers*: Strongly positive ( > https://github.com/w3c/csswg-drafts/issues/2528) The CSSWG issue has 90+ > votes. > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Debuggability > > None > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?It should be possible. > > Flag name on about://flagsNone > > Finch feature nameNone > > Non-finch justificationNone > > Requires code in //chrome?False > > Estimated milestones > > No milestones specified > > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5104141688635392?gate=5084590997504000 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > TAMURA Kent > Software Engineer, Google > > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c2b83372-698a-4420-b169-0bc5f19d8213n%40chromium.org.