- From: Simon Fraser via GitHub <noreply@w3.org>
- Date: Tue, 10 Jun 2025 04:05:54 +0000
- To: public-css-archive@w3.org
I don't object to an async resolution purely for naming, but it wasn't clear to me reading the propose resolution text at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2910778012 that it was just about naming. I don't think a simple scale factor, as exposed by `env(preferred-text-size)`, works here. Here's a graph of the scaling factor (y axis) against the base font size (x axis), based on the the data at https://developer.apple.com/design/human-interface-guidelines/typography#iOS-iPadOS-Dynamic-Type-sizes  From AX1 to AX6, small text gets twice as big, but large text only scales by 1.36. That means that applying a single factor across all text sizes will result in large text getting too large. -- GitHub Notification of comment by smfr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2957615184 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 04:05:54 UTC