Re: [w3c/webcomponents] Using slot="" attribute on <link rel="import"> (Imports without JavaScript) (#636)

@domenic Composing an HTML file from many smaller HTML 'partials' (or 'components', albeit sans the custom tag) is not the same thing as embedding completely separate pages. An `<iframe>` introduces a separate browsing context. What I'm publicly thinking about here is **same browsing context** — whereby CSS and JavaScript loaded by the main page will apply to the composed result as though it were a single page to begin with.

This isn't about "cool and new", but rather what is **already seemingly being done** with web components (see links in my previous comment). I don't think I am misunderstanding web components, I just think that there must be a reason for four separate specifications (e.g. we don't need to use custom elements just because we want to use Shadow DOM), and that some ***inevitable*** uses might be supported without requiring JavaScript. What I'm trying to do is contribute some thinking, and hopefully gain and share some understanding, around how these new standards might be used with respect to a specific case (i.e. 'client-side includes') that is *apparently already being pursued by developers*.

Thanks for the comment!

-- 
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/636#issuecomment-294917385