- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jan 2025 20:20:35 +0000
- To: public-css-archive@w3.org
@fantasai > I honestly think making authors write [longer env() thing] where they currently write [short em thing] is pretty awful and we should try to come up with a better solution. As I said in the call, env() and units are both perfectly workable. We did discuss the possibility of getting multiple values out of the OS fonts, tho - "body" vs "heading" was mentioned during the call, and [Josh Tumath mentions the other font-relative units](https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2551813052). Adding a single `uem` unit seems fine, but duplicating the entire set of font-relative units (`uex`, `ucap`, etc), and potentially doing it *two or more times*, seems bad; some well-chosen env() keywords seem a lot better there. On the other hand, since the use-case is really just MQs and possibly setting font-size on the root, maybe we can avoid all the complication and just stick with a single `uem` and possibly another one or two user-em units in the future. I don't have a strong opinion either way, I just want to make it clear that the constraints we're working with are more complex than your example suggests. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10674#issuecomment-2599127948 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 January 2025 20:20:36 UTC