- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 10 Jun 2025 21:14:08 +0000
- To: public-css-archive@w3.org
@smfr Just to be clear, the async resolution *is* just for naming. The *behavior* was resolved on back in January at the Apple f2f, see [this comment with the resolution](https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2625414100). There was indeed discussion of heading vs body text earlier in this issue, but we resolved on going with a simple solution for now, and deciding later if we still needed to solve more complex cases. (You can, of course, object to the resolution - I'm just making sure that it's clear what the resolution was. However, since the resolution was made months ago, Chrome has started shipping the behaviors; it was just the naming issue that was left before actually exposing the values. So, any behavior changes will need to start considering compat.) @jyasskin Zooming by a uniform percentage isn't the perfect solution, correct, but the current situation (not zooming at all, or zooming by unpredictable amounts depending on whether the heuristics fire for a given block of text) is far worse than uniform zooming. As I said, we discussed this earlier in this issue. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2960597836 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 June 2025 21:14:09 UTC