- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Jan 2014 08:38:31 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23636 Scott Miles <sjmiles@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjmiles@chromium.org --- Comment #4 from Scott Miles <sjmiles@chromium.org> --- I generally think of the inheritance relationship as being non-encapsulating; as opposed to the composition relationship which relies on encapsulation. Polymer uses <shadow>/olderShadowRoot typically to implement inheritance relationships, so by the above it feels natural to remove style encapsulation. By the same token, we would probably favor loosening of the DOM encapsulation too, but I can't say right now what form that would take. However, here are (at least) two arguments against this ticket that I cannot dispute beyond the above. 1. It's awkward for the ShadowDOM machinery to share styles in this manner, and it lacks parallelism vs querySelector. 2. The notions of inheritance vs encapsulation as described above are certainly my opinion. I'm willing to concede this on those points if that's desirous. Last bit: If we kill this issue, I think we need a new (declarative) way to override styling on inherited shadow root. Is there already a syntax for that? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 17 January 2014 08:38:32 UTC