- From: Tatsunori Uchino via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 15:34:40 +0000
- To: public-css-archive@w3.org
> My impression is that the necessary fix is either in the font itself (which is not covered at all by the specification), or in the browser, to work around the bug in the font (which is already allowed by the specification). Ideally both are accepted, but the fix Chromium implemented this time (i.e. the latter) is an exception, as if it were a temporary stopgap to stem bleeding from an artery. Windows has neglected various issues with Japanese (system) fonts for years, and these problems have essentially worsened year after year. It's as if they're treating Japanese users like fools. We should explicitly warn about the flaws in such well-known and widely used fonts within the specification document. > It seems to me that it already supports the kind of fix you want. What change do you propose we make to the specification to fix this issue? A fix is necessary as long as only "may" is used there. For Yu Gothic UI v1.93 or below (I don't know its trunk version where Microsoft insists that they fixed the defect), "should" must be used. Why do you try to force us to warn on this defect in _every_ bug tracker of browsers? This problem has become too well-known as a pitfall. -- GitHub Notification of comment by tats-u Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11074#issuecomment-3347691789 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 15:34:41 UTC