Re: [whatwg/dom] [Declarative Shadow DOM] How should we build the "opt-in" for fragment parsing of declarative Shadow DOM? (#912)

> Why is any of this better than a http / meta equiv header?

> Maybe I misunderstand, but don't all of these opt-in suggestions require JavaScript, which would be contrary to "[compelling use cases such enabling scoped styles without requiring Javascript](https://github.com/whatwg/dom/issues/831)"?

For both of these questions, the answer is that here, we're talking about the **fragment** parser. I.e. for things like `div.innerHTML = contentContainingDSD`. That (by definition) happens in Javascript only, and doesn't happen for document parsing of navigated pages. For these questions, see #913, which is more concerned with server-generated content.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/912#issuecomment-722691239