[w3c/webcomponents] An alternative lazy custom element definition proposal -- conditionalImport (#896)

I'm getting ready to implement an [approach to lazy loading custom elements](https://github.com/bahrus/xtal-sip), an alternative to [this proposal](https://github.com/w3c/webcomponents/issues/782), and see how it goes.

I'm raising this issue, because it may contain useful features not found in the above proposal.  It's clearly not a "spec" but I'm hoping it could be considered as something that would benefit the platform.  I'd like nothing better than to hear that I'm wasting my time implementing what I'm about to implement, because the need for this seems so apparent to others, and help is on the way.  It provides an approach to the issue of providing hash integrity, which @annevk  has raised as a concern.

I believe I remember reading that Firefox found something like this to be quite useful when it implemented its UI with web components.

The primitives exist to implement all aspects (except for import maps), so it's kind of a "second-order" proposal, like how microwaves enhanced cooking, but didn't necessarily open up that was impossible before..

Which brings me to the other point I wanted to raise with this issue  and linking document -- I'd like to add my (unwashed) voice to those who are requesting Firefox and Safari either provide a gentle nod of approval towards import maps, or propose an alternative, or bring up a showstopper.



 

-- 
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/896