This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This is a spin-off from Bug 23170. Sharing defaultView could have big implication and may need better framework on HTML side so that such a conceptulization can fit in the picture. For the first cut, it might be better to cover which should be loaded for imports feature-by-feature, instead of describing it in abstract way.
By the way, why should stylesheets be loaded? It's because this allows script-supported CSS framework like Bootstrap being an import. Also, UI framework can pack its default "theme" as an import in addition to the script itself.
Working on this... https://github.com/w3c/webcomponents/commit/99d0f1d8b1d6a993e811c8e9ea670396b783aff3 Turns out de-dup for stylesheet is tricky to define, especially because there is a demand that wants to define the order or appearance based on the position of <link> element. Think about this example: - index.html <link> - a.html <style id="s0"> <link> - a.html In this case, should styles in a.html win styles in s0? If we styles in imports behave like scripts, it shouldn't and s0 should win because a.html is already imported and second a.html is just skipped. But style behaves differently in general. For example, unlike <script>, DOM mutation matters for <style>. If it is moved in different location, the order of the style changes. So saying "already imported" doesn't provide good mental model.
Closing as it is dumped into the ToT [1]. We certainly need more polish though. I'll do it by filing finer-grained bugs (starting from Bug 24756), so that it makes the point clear. [1] http://w3c.github.io/webcomponents/spec/imports/#style-imports