[Bug 19562] New: [Shadow]: Consider making shadow DOM subtrees public by default

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19562

          Priority: P2
            Bug ID: 19562
          Assignee: dglazkov@chromium.org
            Blocks: 18428
           Summary: [Shadow]: Consider making shadow DOM subtrees public
                    by default
        QA Contact: public-webapps-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: dglazkov@chromium.org
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Component Model
           Product: WebAppsWG

This is a spill-over from bug 15409.

There's been several comments from developers about the fact that Shadow DOM
encapsulation is _too_ well-sealed for various long tail, but important use
cases. In other words, the information that could be accessible (no security
concerns, for example) is not. One has to use hacks to get at the truth.

A proposed solution strawman:

I buy this and want to help. Here's the latest strawman:

1) There's a 3-position switch on each shadow DOM subtree: public,
private, isolated.

2) There's a mechanism in place to flip this switch (specifics TBD)

3) the element.shadowRoot property points to the top of the tree
stack, or null if the shadowRoot's subtree is in "private" or
"isolated" setting.

4) <shadow>.olderSubtree points to the older subtree in the stack or
null if the older subtree is in "private" or "isolated" setting.

5) ShadowRoot.host points to the shadow host or null, if the subtree
is in "private" or "isolated" setting.

6) The "isolated" setting essentially means that there's a new
document and scripting context for this shadow subtree (specifics
TBD). Watch https://www.w3.org/Bugs/Public/show_bug.cgi?id=16509 for
progress.

Remaining questions:

a) how is the switch flipped and when?

b) do we want to introduce the concept of removing shadows subtrees
from the top of the stack? Seems like a completeness thing.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.