Re: [WICG/webcomponents] Allow customElementRegistry definitions to persist across page loads (Issue #1033)

Piggybacking on idea...

Looks like we are on the edge of breaking the **DOM passing across threads** prohibition rule.  The  **WC L**ibrary ( and in general any ) could have a use for bundle globals initialization and keep as registry for this lib as the implementations. Lib URL would serve the artificial context(hidden page/thread). The consumer page would refer the lib by URL on one of layers enabling its custom elements there. 

The life cycle would start with 1st use and close upon session termination with ability to discard any time on browser discression. 


Of cource there would be no domain nor document in the scope of WCL. Those would become available only during WC instantiation. Such restrictions can be lifted if lib domain and consumer page match. 

WCL would encourange CDN kind deployments and reuse. With security ^^ in place,  

### preloading
as usual via `meta` tag 

### embedding into scope of WC
* declarative - same `meta` resource?
* imerative - import as JS module. Perhaps with own `assert`-ion.


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

Message ID: <WICG/webcomponents/issues/1033/1744125591@github.com>