- From: <bugzilla@jessica.w3.org>
- Date: Tue, 06 Aug 2013 16:45:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22892 --- Comment #4 from Tab Atkins Jr. <jackalmage@gmail.com> --- Actually, I think I've been barking up the wrong tree anyway. The entire point of <style scoped> is solely to make it easier and less error-prone to target only a particular element and its descendants. You should be able to replace <style scoped>:scope p</style> with <style>#parent p</style> without any change in meaning or targeted elements. So, same thing here. The <style scoped> is scoped to the host element, and naturally applies its selectors on the light dom side, since that's where it lives. It shouldn't target anything in the shadow dom unless you let selectors through. (Where it gets distributed into the shadow dom shouldn't make a difference - it's scoped to its original parent.) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 6 August 2013 16:45:56 UTC