- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 19:56:55 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20144
brian kardell <bkardell@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bkardell@gmail.com
--- Comment #7 from brian kardell <bkardell@gmail.com> ---
It seems to me that there are different concerns you might talk about, not
entirely unlike sandboxed iframes. Shadow DOM (as currently) provides a nice
simple membrane to keep lots of accidental things from going wrong, but can be
easily traversed into/pierced and doesn't get a separate execution context or
anything special. If we had a ::parts concept it would be useful to explain
what that means in terms of CSS and DOM boundaries, etc.
Is it possible to consider, instead of a flag, that a shadow root has a set of
properties (which I hope default to what they currently are in canary,
personally). This would probably help explain things in the platform even if
we never entirely enable them in author space, if you see what I am saying.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 24 February 2014 19:56:56 UTC