- From: Stephen Chenney via GitHub <noreply@w3.org>
- Date: Mon, 26 Jan 2026 15:05:18 +0000
- To: public-css-archive@w3.org
I added Agenda+ because it seems there may be disagreement or varying use-cases for the highlight inheritance crossing shadow boundaries, but then again I see no other way this could work and that it is consistent with typical behavior for other properties. I believe the current intent is for highlight inheritance to cross shadow boundaries because we would expect the page to have a consistent selection and highlight styling unless the component explicitly defines otherwise (which would then be inherited within the component). So this really is just editorial. Two things to address: * The cited text in [the comment above](https://github.com/w3c/csswg-drafts/issues/12497#issuecomment-3576162344). Honestly it makes no sense to me at all. * The text in https://drafts.csswg.org/css-pseudo-4/#highlight-cascade that says: "its [specified value](https://drafts.csswg.org/css-cascade-5/#specified-value) is determined by inheritance from the corresponding [highlight pseudo-element](https://drafts.csswg.org/css-pseudo-4/#highlight-pseudo-element) of its [originating element](https://drafts.csswg.org/selectors-4/#originating-element)’s parent element." to make clear that it's parent or host when parent is a ShadowRoot, or that it's working in the flat tree. -- GitHub Notification of comment by schenney-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12497#issuecomment-3800058578 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 January 2026 15:05:19 UTC