Re: [whatwg/dom] Composed shadow DOM (#531)

> Having only CSS encapsulation is much easier than having both CSS encapsulation and DOM encapsulation

I didn't actually say that, I don't think. I certainly didn't mean it. I can respect that it'd be difficult to fundamentally separate the two. I assumed that engines had some sort of data-stricture such as a hash map between elements and selectors. However, I was also making the assumption that the public interfaces could be selectively patched depending on which method (declarative `composed` attribute / imperative `attachShadow()` method) is used. I know little about the implementation details and wish I had more time to understand them to craft a proper proposal with them in mind. I don't mean to waste anyone's time here.

I would think that if you separated the two, you'd have two mappings:

1. for the DOM tree being scoped for CSS
2. for the unscoped DOM tree for the public interfaces to operate on

When DOM encapsulation is switched on, you already have the first tree that operates on the scoped tree and can throw out the old one.


-- 
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/531#issuecomment-341619959