- From: Lonnie Best <notifications@github.com>
- Date: Wed, 24 Apr 2019 05:59:44 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 24 April 2019 13:00:06 UTC
Imagine how much extra work is being done right now because of the fact that a browser cannot load a web page directly from a javascript file. It must be html. Read this: https://stackoverflow.com/questions/55789770/loading-a-web-page-directly-from-a-javascript-file-exclusively Can you think of anything, right now, that is being developed by standards committees, that could be completely eliminated, if the browser would support client-side javascript as an entry-point to a web page? Often, people do a lot of work on something because they do not realize a more fundamental flaw, that if corrected, would eliminate mountains of work. The readers of what I'm writing right now, are abstract thinkers. Just think about what I'm saying.... -- 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
Received on Wednesday, 24 April 2019 13:00:06 UTC