- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Tue, 13 Jan 2026 15:43:41 +0000
- To: public-css-archive@w3.org
Currently, [`css-shadow`[`-1`]](https://drafts.csswg.org/css-shadow/) already resolves, but both [`css-scoping`[`-1`]](http://dev.w3.org/csswg/css-scoping/) and [`css-shadow-parts`[`-1`]](https://drafts.csswg.org/css-shadow-parts/) yield _Bikeshed pending_ error pages instead of the expected redirects. The [repo overview](https://drafts.csswg.org/) still only lists the the old ones, not the merged document. The [Index](https://drafts.csswg.org/indexes/#selectors) has also not been updated yet. In TR space, there is a [very old WD for Scoping](https://www.w3.org/TR/2014/WD-css-scoping-1-20140403/) and a [very recent WD for Shadow Parts](https://www.w3.org/TR/2025/WD-css-shadow-parts-1-20251216/). For what it is worth, I find the name chosen for this CSS module most unfortunate! CSS has _text shadows_ and _box shadows_ (with several properties and grammar productions named accordingly), as well as a `drop-shadow()` filter function. Confusingly, this "CSS _Shadow_ Module" is not about any of these styling-related topics. Instead, the module is about a DOM concept and, accordingly, it does not introduce any new properties or values to CSS, just several _selectors_ (i.e. pseudo-classes `:host`, `:host()`, `:host-context()` and `:has-slotted` and functional pseudo-elements `::slotted() ` and `::part()`, as of writing this comment) and even *generic(?) host document attributes* (`part` and `exportparts`), which surely should be something left to the respective document language standards like [HTML](https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements) and SVG, or perhaps to the specification of the [DOM ](https://dom.spec.whatwg.org/#shadow-trees). A previous WD had introduced a [`::shadow` pseudo-element](https://www.w3.org/TR/css-scoping-1/#shadow-pseudoelement), but that is apparently gone for good (or just for now?). Before advancing this ED to WD, I would therefore strongly suggest the CSSWG reconsidered the (full and short) name and the scope of this specification. From the little I understand of the topic and inspired by the precedence set by ["Non-element Selectors" `selectors-nonelement`](https://drafts.csswg.org/selectors-nonelement/), I offer the suggestions "Component Selectors" `selectors-component`, "Hosted Selectors" `selectors-hosted`, "Scoped Selectors" `selectors-scoped` or, if you really must, "Shadow Selectors" `selectors-shadow`. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13333#issuecomment-3745052004 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 January 2026 15:43:42 UTC