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

Sigh. Brinkmanship isn't an attractive look.

* The OP (and [the original bug](https://www.w3.org/Bugs/Public/show_bug.cgi?id=27380) it was migrated from) doesn't have detail either way, it just references "document-internal references"
* [The second reply](https://github.com/w3c/webcomponents/issues/179#issuecomment-197707458) (first substantive reply) talks about `filter: url(#frag)`.
* [The fourth reply](https://github.com/w3c/webcomponents/issues/179#issuecomment-197976839) talks about `fill: url(#frag)`
* [The ninth reply](https://github.com/w3c/webcomponents/issues/179#issuecomment-219085396) links to [an earlier email](https://lists.w3.org/Archives/Public/www-style/2016May/0114.html) asking about `mask: url(#frag)` 
* [The tenth reply](https://github.com/w3c/webcomponents/issues/179#issuecomment-274332039) is the very first mention in the entire thread of `<use href>`.
* [The sixteenth reply](https://github.com/w3c/webcomponents/issues/179#issuecomment-321024550) is *you yourself* mentioning *both* `filter` and `<use>`

I could go on, but no, trying to claim that this issue is just about `href` attributes is absolutely wrong. You are right that `href` attributes, because they don't inherit, don't need to *worry* about inheritance semantics. But **this issue** can't be resolved without talking about inheritance semantics, because most of it is talking about inheritable CSS properties.

That said, the current proposal to solve the non-inheriting `href` attributes by saying that they're scoped to the shadow tree they appear in is just fine. It's not affected by however we decided to handle inheritance semantics. There's absolutely no problem with resolving on these `href` semantics *right now*.

I'm just saying that we can't close *this issue* as resolved without talking about inheritance, because it's been about inheritance from the very beginning.

> I'd rather resolve that issue first before resolving other CSS global namesspacing issue especially because that's a concern of CSS WG, not SVG or Web Platform WG.

While we generally consider these to be more CSS-ish these days, they're all present in plain, CSS-less SVG as well; `<rect fill="url(#frag)" />` still needs to define how it works in shadows.  This is a general problem with inheritable values; it's not scoped to CSS itself.

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