- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Mar 2015 08:15:18 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28185 Bug ID: 28185 Summary: [Shadow]: TextNode should have getDestinationInsertionPoints() Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: hayato@chromium.org QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, public-webapps@w3.org Blocks: 14978 In the current spec, only Element has getDestinationInsetionPoints: http://w3c.github.io/webcomponents/spec/shadow/#widl-Element-getDestinationInsertionPoints-NodeList partial interface Element { ShadowRoot createShadowRoot (); NodeList getDestinationInsertionPoints (); readonly attribute ShadowRoot? shadowRoot; }; However, because not only Element, but also TextNode can be distributed, getDestinationInsertionPoints should be defined also in TextNode. One idea is to let Node have getDestinationInsertionPoints rather than Element: Idea A:: partial interface Node { NodeList getDestinationInsertionPoints (); }; Another idea is to let TextNode have getDestinationInsertionPoints, in addition to Element: Idea B:: partial interface Element { NodeList getDestinationInsertionPoints (); }; partial interface TextNode { NodeList getDestinationInsertionPoints (); }; Which should we prefer? -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 10 March 2015 08:15:20 UTC