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

I like this idea, but the DOM Centirc mindset will be hard to break. At their heart, browsers are viewers for "traditional" documents - text files. Over time they have become much more. Writing a form driven application for browers is in many ways like writing applications in MSWord with macros - it's not a "document", but it needs to be crammed into a document. Then we need to deal with document artifacts, like how white-space is handled. The Window should support multiple "viewer" types, one being DOM/window.document. But we could have options like window.svg or window.mediaplayer. In these cases there would be no `document`/DOM, another view engine would replace it. The problem is that functionality that could go on `window` (having nothing to do with a "actual document") continues to get placed on `document` . Being able to start from a non-html source would be a step twords ditching the DOM altogether.

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