- From: szager-chromium via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 May 2024 02:32:10 +0000
- To: public-css-archive@w3.org
@fantasai -- jfkthame made the same point about "hanging glyph" in a code review [comment](https://github.com/w3c/csswg-drafts/issues/10066#issuecomment-2088122192); I updated the PR to correct the language. For `box-shadow`, I deliberately placed the new text just after the illustrated example that shows the effect of spread and blur; I felt that it added clarity to the specifics of the geometry. I agree that `border-image-outset` doesn't need any clarification. More generally, although the language added to `text` and `text-decoration` is squishy and non-normative, it might also be useful for developers who want to reason about the extent of ink overflow. Specifically, the de facto (within 2px) consistency of ink overflow extent between different implementations for a given well-defined font, and the effect of using the `from-font` keyword where supported for text decorations, might be useful guidance. Maybe they belong in the IntersectionObserver spec rather than in `css-text` or `css-text-decoration`; or maybe they belong in a blog post or a tweet instead of a spec. That's the question I'm hoping to resolve. -- GitHub Notification of comment by szager-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8649#issuecomment-2121594331 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 May 2024 02:32:11 UTC