3 ms·
The JS module system is actually better suited for this. And ultimately HTML imports don't solve any of the cross-package import issues that JS modules are sti
by spankalee 6y ago
The JS module system is actually better suited for this.
And ultimately HTML imports don't solve any of the cross-package import issues that JS modules are still trying to solve.
- elcritch 6y agoPerhaps, but as a web developer html imports let me pull in and use web-components without writing any Javascript. Give an HTML editor to a 15 year old, some links to a decent web-component library and they're off to the races without mastering JS.
- goatlover 6y agoExactly this. Why should JS be required for something the browser could handle when we're talking about HTML?
- saalweachter 6y agoHell, you'd think it'd be a bigger thing among the noscript/privacy world to be able to do more things without JS.
- elcritch 6y agoUnfortunately, web components always require JS to work. However, they can hide the JS from the user. Though I suspect that it'd be fairly easy to "whitelist" web-component CDN libraries and disable other JS still.