Re: [csswg-drafts] [css-shadow-1][editorial] Add a note for the merge and renaming (#13333)

> 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.

Added the redirects in https://github.com/w3c/csswg-drafts/commit/6c8b4a5f525b488bd8a69fe38d72cd99a4cd3418.

The [repo overview](https://drafts.csswg.org/) still only lists the the old ones, not the merged document.

Updating of the overview page is broken for months now. See #12743.

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/).

I've made a little editorial change in https://github.com/w3c/csswg-drafts/commit/5cb09efb77f9b30639f350014105c24d122f9f1c, so an update of CSS indexes is triggered. That should fix the issues.

@Crissov If you still issues, please file a separate issue.

> 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?).

This issue is about adding the note for the merge of CSS Scoping 1 and CSS Shadow Parts 1 and renaming, which was resolved on in https://github.com/w3c/csswg-drafts/issues/5809#issuecomment-910896765. If you disagree with the renaming, please file a new issue.

> 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`.

There's #6370 requesting to publish CSS Shadow 1 as WD. You may voice your concerns there or create a new issue and refer to that one. Again, this issue is limited to the editorial change of adding a note for why the CSSWG decided to merge the two specs and rename them.

-----

I've now added the note in https://github.com/w3c/csswg-drafts/commit/b3e9ad4b6e311b872268252921f000dab099e181. Therefore I consider this issue as done.

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13333#issuecomment-3759257542 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 16 January 2026 10:17:35 UTC