Re: [w3c/webcomponents] Make JavaScript Files a Valid Entry Point to a Web Page (#807)

Yeah.  The portability is a good point.  In my experience, the JS file that initializes the document often is more entangled with the application that more ancillary files.

If you pick an extension (something better than `.js.html` that doesn't overlap) and document the server side approach and or the polyglot hack and enough people like it, you'll find it a lot easier later to convince browser vendors to standardize it.  The non-overlap is what would allow it to be accepted widely without having to prove backwards compatibility with existing security assumptions, which means that anything that ends with `.js` or `.mjs` would be a problem.

Bikeshedding: `.js.webapp`

-- 
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/807#issuecomment-490513773