[Bug 16458] New: [Shadow]: Consider named template sets

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

           Summary: [Shadow]: Consider named template sets
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Component Model
        AssignedTo: dglazkov@chromium.org
        ReportedBy: bkardell@gmail.com
         QAContact: public-webapps-bugzilla@w3.org
            Blocks: 14978


Not sure if this is worth it...

Consider adding named templates to a collection on the ShadowRoot.  Many
systems for dealing with templates now "hold on" to the references and deal
with them by name to avoid re-lookups.  The browser maintains numerous indexes
like this already and the advantage to doing it at that layer is that it is
easy to remove templates from the collection as they are removed from the DOM. 
Currently, that's a problem in some implementations.

Adding some IDL explaining what I am saying...

[Constructor(in HTMLElement host) raises (DOMException)]
interface ShadowRoot : DocumentFragment {
    HTMLElement getElementById(in DOMString elementId);
    NodeList getElementsByClassName(in DOMString tagName);
    NodeList getElementsByTagName(in DOMString className);
    NodeList getElementsByTagNameNS(DOMString namespace, DOMString localName);
    attribute bool applyAuthorStyles;
    readonly attribute Element host;
    readonly attribute Element activeElement;
    readonly attribute Selection selection;
    attribute DOMString innerHTML;
    DocumentFragment getTemplate(DOMString name);

}
ShadowRoot implements NodeSelector;


dictionary Template {
  DOMString name;
  DocumentFragment template;
};

-- 
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 Tuesday, 20 March 2012 21:05:26 UTC