Re: [WICG/webcomponents] April Face-to-face Scheduling/Agenda (Issue #1050)

### Scoped Custom Element Registries

#### Chrome Prototype Feedback

* `createElement` works
* `importNode` does not work; therefore _**cannot be used in Lit**_
* _Issue:_ global registry applies in scoped registry; can be confusing
* _Issue:_ setting `innerHTML` does not work, even if element is connected in scoped shadowRoot

This behavior verified on Canary 126.0.6452.0. The prototype hasn't been updated since [1/24](https://chromium-review.googlesource.com/q/hashtag:%22scoped-registry%22+(status:open%20OR%20status:merged)). Is additional work planned?

#### Polyfill Usage/Issues

* surprising amount of use within the Lit community, often by organizations using a micro-frontend architecture and supporting a variety of web frameworks
* significant number of [issues](https://github.com/webcomponents/polyfills/issues?q=is%3Aissue+is%3Aopen+%5Bscoped-custom-element-registry%5D); many related to `formAssocated` which is currently always true in polyfill.


#### Spec Issues
* #1040: is it possible to have disconnected elements use the registry from the last scope to which they were connected?
* #1043: introducing new rendering APIs adds significant adoption friction especially for frameworks
  * main concern is conflicts with the global registry
  * discuss possibility of adding 'upgrade only' elements to address this

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

Message ID: <WICG/webcomponents/issues/1050/2091097913@github.com>