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

Ok, let me spell this out more concretely.

There is work being done right now on html templates the would be completely unnecessary if a fundamental flaw was corrected in the standards.

That fundamental flaw, is the fact that you cannot load a web page by going directly to a client-side javascript file.

For example, if I created a client-side javascript file, that dynamically generated html and css and place it on a web server at: www.webpage.com/index.js, the web-broswer would simply show the source code of that file, it would not run the file. That is fundamental flaw in the standards. A client-side javascript file, that dynamically creates an html document should be first class citizen of the web and it should not require a static html file to launch a page created that way.

-- 
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-486245518