Re: [WICG/webcomponents] How should various document internal references work when SVG is being used in shadow DOM (#179)

From https://github.com/WICG/webcomponents/issues/179#issuecomment-438838649, this issue really contains three sub-issues:

> Here are the current blockers for this issue:
> 
> * [SVG use element can't reference an element within the same shadow tree](https://github.com/w3c/webcomponents/issues/772)
>   
>   * [[css-values] Clarify fragment URLs resolve against the current tree, not document tree](https://github.com/w3c/csswg-drafts/issues/3320)
> * [Clarify how fragment URLs are resolved within shadow trees](https://github.com/w3c/csswg-drafts/issues/2715)
> * [[css-scoping] Handling global name-defining constructs in shadow trees](https://github.com/w3c/csswg-drafts/issues/1995)

Of those, the first one seems to be resolved, down to actually modifying the spec. I.e. browsers agree on behavior - SVG elements can reference other elements within the same shadow tree. Is that correct?

The second one is about expanding fragment references to be able to cross shadow boundaries. I'm not sure there's appetite for that change or not, but there has been very little discussion on that issue.

The last one really isn't about SVG specifically, but is about other global name defining things (e.g. `@font-face`). That one is very much unsolved.

Is the above an accurate summary of the state of this issue? If so, I would propose closing this issue, since the sub-parts are well-tracked in the linked issues.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/179#issuecomment-809830587