robglidden

The 1a [current spec text](https://html.spec.whatwg.org/#link-type-expect:~:text=equal%20doc's%20URL%20with%20exclude%20fragments%20set%20to%20false) processes an internal reference link given the element's node document, yes? To reach out of a shadow, some sort of fit-to-purpose [tree-scoped reference](https://drafts.csswg.org/css-scoping/#shadow-names) resolution spec...

To me, a key question to answer is how would any algorithm -- 1, 2, 3 or probably any other -- handle duplicate identifiers. It is hand-wavy to say that...

I would say "red red red" is the [best answer](https://github.com/whatwg/html/issues/11364#issuecomment-2964720972) above, i.e. first `` in tree order expanded to include shadow trees. Advantages: - fully supports streaming SSR (HTTP Transfer-Encoding:...

> I want to point out what I think is a critical detail: we already have cross-scope style sharing in the form of adoptedStyleSheets. What we're looking for is a...

> - That new attribute is a space-separated list of IDs pointing to the IDs from the stylesheet comments. Maybe I don't understand the idea of comment-based global `` IDs...

@justingnani: server-generated unique IDs, machine-generated or otherwise, would of course still work fine as they do now. But that in itself does not create a need to require only machine-generated...

>>I also don't think it's a good idea to mix URLs and same-document references due to base URLs and such. It's rather messy. >I agree that base URL's add some...

> An alternate proposal for this could be to use a new URL scheme, similar to data: and blob:, that only targets same-document elements, where the path of the URL...

Here is a [thought-exercise repo](https://github.com/htmlcomponents/declarative-imports) that demos using import maps, which already in Chrome support CSS modules from files and (could?) sidestep or at least scope the specifier attribute issue,...

I think [HTML modules](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/html-modules-explainer.md) and [recently here](https://github.com/WICG/webcomponents/issues/1059), are [due](https://github.com/WebKit/standards-positions/issues/285) for a back-to-basics [TAG design re-review](https://github.com/w3ctag/design-reviews/issues/334#issuecomment-529789278) in light of modern developments of import attributes, import map constraints and DSD as well...