- From: <bugzilla@jessica.w3.org>
- Date: Thu, 16 Jan 2014 23:17:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23636 --- Comment #3 from Elliott Sprehn <esprehn@gmail.com> --- (In reply to Elliott Sprehn from comment #2) >... > > It also means you need to be super careful not to collide with your > superclass with class names so even though you can use the same id in both > of them like #container and then this.$.container in polymer, you can't > style them separately because the CSS ends up applying to both. > It seems Polymer already has this issue, if you have an id conflict then this.$.container will always be the one from the youngest shadow root. So I can understand why allowing conflicts for div { display: none; } doesn't seem like an issue as Polymer already has an opinion that you just shouldn't do that. Previously CSS matched the same as querySelector() so if <style> in any ShadowRoot applies to all others on that element why doesn't shadowRoot.querySelector("div") return ones in all the other ShadowRoots? Or why doesn't root.getElementById("x") return things from the older shadow root like this.$ would? Can you give examples why you want DOM level encapsulation but no style encapsulation? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 16 January 2014 23:17:02 UTC