- From: Josh Tumath via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jan 2025 01:36:36 +0000
- To: public-css-archive@w3.org
Great. Yeah I agree that a unit like `uem` would be the only one needed for the main use cases outlined above. This is what I would like to propose, then: **A new length unit called `uem` (name can be bikeshedded). `1uem` is equivalent to `16px` when the user agent/operating system's font scaling is set to the default value. If the user increases the UA/OS font size by 200%, `1uem` is equivalent to `32px`.** If we do still want one or more env() keywords, perhaps they could refer to the _actual_ operating system's font sizes, which could be different per platform. So for example, `env(body-font-size)` might (with default OS a11y settings) be 15px on one OS and 13px on another. And that would be the differentiator with the proposed `uem` unit: the `uem` unit would be relative to 16px whereas the env() would provide the _actual_ OS font size. How do people feel about that? If no one disagrees, I'll add it to the agenda. -- GitHub Notification of comment by JoshTumath Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2603454418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 January 2025 01:36:37 UTC