- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Mar 2024 21:56:25 +0000
- To: public-css-archive@w3.org
> "for a given well-defined font and text input, across browser implementations, the maximum possible extent of ink overflow from hanging glyphs is no more that a 2px outset from the painted area determined by visual inspection in any conforming browser." This seems a bit unsatisfactory to me, because I think there are a number of factors it ignores. As an author, you can't actually be sure what font will be used to render the content on the user's machine. Your carefully-chosen webfont may have failed to load, for any of various potential technical, policy, or user-preference reasons. So the user may end up seeing a substitute or fallback font that has very different overhang characteristics. In addition, the user may have set a min-font-size preference in their UA (e.g. for accessibility reasons) that mean the text is being rendered at a different size than you expected, resulting in greater overflow. Or they may have an accessibility feature that adds a high-contrast opaque background behind text elements, potentially extending more than 2px outside the glyph bounds. So if it's necessary for authors to reason with absolute certainty about this for security reasons, I think the proposed text here falls short, and potentially gives a false assurance. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8649#issuecomment-2010712895 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 March 2024 21:56:27 UTC