- From: Mason Freed <notifications@github.com>
- Date: Tue, 15 Sep 2020 15:25:51 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/webcomponents/issues/871/693011908@github.com>
> With that amendment, it seems like declarative Shadow DOM would be compatible with closed shadow trees so we can assume this technical issue has been resolved. Great. I've added two more spec PRs for this change, one in [HTML](https://github.com/whatwg/html/pull/5921) and one in [DOM](https://github.com/whatwg/dom/pull/893). This makes four open PRs here, which could use reviews: 1. [(HTML) Prevent attachInternals() use before custom element constructor](https://github.com/whatwg/html/pull/5909) 2. [(HTML) Add ElementInternals.shadowRoot](https://github.com/whatwg/html/pull/5912) 3. [(HTML) Prevent access to ElementInternals.shadowRoot for pre-existing shadow roots](https://github.com/whatwg/html/pull/5921) 4. [(DOM) Add is-available-to-element-internals](https://github.com/whatwg/dom/pull/893) > There is still a pending question of whether we support the declarative Shadow DOM at conceptual level. I need to get back to you on that. Ok, thanks for the update. I would really appreciate your thoughts soon - we are proceeding with an Origin Trial as we speak, and I'd love to ship this feature soon. I would prefer not to do that without your input and support. As I [mentioned in the main thread](https://github.com/whatwg/dom/issues/831#issuecomment-673625206), I believe the currently-proposed solution is worthwhile, for reasons other than pure performance. -- 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/871#issuecomment-693011908
Received on Tuesday, 15 September 2020 22:26:04 UTC