- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Nov 2023 09:29:18 +0000
- To: public-css-archive@w3.org
I've definitely seen fonts with incorrect bounding-box data, though I don't recall the specific examples, and this did result in clipped rendering in some context (which is what led to investigating the font data), while in other environments the glyphs rendered fully. One point to note with regard to OpenType bounding boxes is that they represent the bounding box of the glyph geometry, but do not account for the fact that at rendering time, the effects of grid-fitting and antialiasing may mean that pixels just outside the "theoretical" glyph bounds are actually affected. And how do the extents in the 'head' table work in the case of variable fonts? Do they indicate the maximum bounding box under any combination of variation settings, or the bounding box of the default instance? The spec does not appear to provide for applying deltas to these fields, AFAICS. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8649#issuecomment-1798123347 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 November 2023 09:29:20 UTC