- From: Roman Komarov via GitHub <noreply@w3.org>
- Date: Thu, 20 Nov 2025 09:39:36 +0000
- To: public-css-archive@w3.org
This sounds interesting, but aside from the non-stable rendering depending on the initial zoom value, there could be concerns over the ability to detect if the user uses zoom. BTW, I am currently using my prototype implementation with the 200% limit on my blog, and, so far, it seems to work pretty well. The default `font-size` that I have in most cases is enough to scale the headers to fit the full width, occasionally I have to bump up the default `font-size` if the words are too short, and very rare there is a need to define different values per line, but usually it is not more than 1 line needed, and with a native implementation `::first-line` will help. What I mean: I still think the default limit is the most simple way to address it, so I will repeat my question: > I would be interested to know reasons why Chrome's team thinks why this limit won't work well. That said, if your experiments succeed, and won't be blocked by some concerns, it could potentially _augment_ the limit: by default there could be a limit, thus eliminating the issue and not requiring the zoom detection. If an author overrides the limit to more than 200% (or maybe even 250% — or could be dependent on the UA's max page zoom level?), _then_ this additional algorithm could kick in, maybe? -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3556902596 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 November 2025 09:39:37 UTC