- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 02:44:05 +0000
- To: public-css-archive@w3.org
While this is clearly a problem, it's not clear to me that it is a problem with the specification, which is what this repository is about. Good fonts are ideal, but I believe that the specification gives enough leeway to browser engines to work around bad ones if they happen. Based on this, while font vendors and browser vendors can have some work to do to make the situation great, I don't think there's anything about the specification that needs to be changed to address the situation. Does that seem right? If so, I propose closing this issue as out of scope. Not to say that it's not an issue, just that it isn't one that calls for spec changes. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11074#issuecomment-3344657020 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 September 2025 02:44:06 UTC