Re: [w3c/webcomponents] HTML Modules as a leaf node in the module graph or not? (#805)

I work in a place that uses iFrames out the gazoo.  Mostly to host client-centric applications (like extjs / angular / preact), sometimes to host server-side solutions.  iFrames have been very powerful, but quite frustrating at the same time, so I'm really hoping HTML Modules can help us move to a much better solution.

I like the way sandboxed iFrames allow you to specify what features are allowed, including whether scripting is allowed.  Maybe both models could be supported?  I could see scenarios where a site doesn't want any dependency script to load on its own (if I squint hard enough).

I think it's critical that the HTML Module be able to specify dependencies, and that the consumer can resolve them properly (maybe with the help of import maps).  Without that, the usefulness of HTML Modules goes way down in my opinion.

At the other extreme, it would be great if HTML Modules could be imported from a CDN just like js modules can.

Basically I want everything (but of course I want the browser to be secure, so I recognize there's a balancing act with CSP's and all that).

-- 
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/805#issuecomment-479955094