- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 May 2024 10:31:20 +0000
- To: public-css-archive@w3.org
Hmm... I was quite surprised when I didn't see "as specified" in the spec text and thought it's a mistake or something, but it makes sense now with @jfkthame's example. So I'm switching my position :) Leaking/Exposing font data via computed style is probably not a big issue, as we already have a lot of precedences (like the absolutization of `ex` unit in computed values). So we can allow one more here. And it should be better if we have a note/example in the spec to explain the rationale. -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10292#issuecomment-2109847585 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 May 2024 10:31:20 UTC