- From: <bugzilla@jessica.w3.org>
- Date: Wed, 12 Feb 2014 02:17:19 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24616 --- Comment #2 from Morrita Hajime <morrita@google.com> --- 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 12 February 2014 02:17:21 UTC