- From: Tatsunori Uchino via GitHub <noreply@w3.org>
- Date: Sun, 19 Oct 2025 14:38:06 +0000
- To: public-css-archive@w3.org
> I don't know if would be fair to font vendors / OS vendors / browser vendors if we don't try to have broad and balanced coverage. Depends on how much the vendors tend to listen to or accept feedback from users. e.g. Microsoft is terrible. Feedback Hub is not working at all. Microsoft tends to try to sweep issues concerning its own products (e.g. abduct local data of innocent users to OneDrive and discard it / disguise “Update and Restart” as “Update and Shutdown”) under the rug whenever possible. > The specification is not the boss of browsers, the specification is what browsers (and others) agree we are trying to do. I think the suggested fix you proposed is reasonable, but accepting it will not automatically fix or even report bugs in all browsers for every broken font. Something like "Tips for implementers" is needed. https://github.com/tats-u/markdown-cjk-friendly/blob/main/implementers-tips.md -- GitHub Notification of comment by tats-u Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11074#issuecomment-3419717039 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 19 October 2025 14:38:06 UTC