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

While I'm sad I missed the discussion (I had to head home Friday morning), I'm very happy y'all agreed with me and went with local-only. I wish y'all had been able to discuss it on Thursday when I could have been there, tho, because I could have explained why you actually **can't** exclude my part (3).  

It's required to represent inherited values.  Without it, for example, what happens when the outer page sets `body { font-family: some-network-font; }`, then the shadow DOM asks for the computed value of `font-family` on one of its elements? You can't say `some-network-font`, because that doesn't round-trip; the outer page's `@font-face` defining that font isn't visible to the shadow. (And the shadow might have defined its *own* `@font-face` of that name; the component shouldn't have to worry about name conflicts with the outer page!)

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