W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18535] New: [Custom]: Scoping of element definitions in Shadow DOM

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Aug 2012 23:16:33 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-18535-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18535

           Summary: [Custom]: Scoping of element definitions in Shadow DOM
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
        AssignedTo: dglazkov@chromium.org
        ReportedBy: dglazkov@chromium.org
         QAContact: public-webapps-bugzilla@w3.org
            Blocks: 14968


Should element definitions (the <element> thingies) be scoped inside
of a shadow DOM subtree?

That is, in parallel with id/name/selector scoping, would it make
sense to do the same with element definitions?

This means that you will have to explicitly state which components you
want to use inside of each <element>, but also means that you can have
a whole set of internal components that aren't surfaced to the
document.

Example:

Bob has framework A and framework B used on his page. Both define
x-qux, and A one wins. Bad news for framework B, which happens to also
use it in its components.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 August 2012 23:16:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 10 August 2012 23:16:44 GMT