This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28185 - [Shadow]: TextNode should have getDestinationInsertionPoints()
Summary: [Shadow]: TextNode should have getDestinationInsertionPoints()
Status: RESOLVED DUPLICATE of bug 28069
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14978
  Show dependency treegraph
 
Reported: 2015-03-10 08:15 UTC by Hayato Ito
Modified: 2015-03-10 08:37 UTC (History)
2 users (show)

See Also:


Attachments

Description Hayato Ito 2015-03-10 08:15:18 UTC
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?
Comment 1 Hayato Ito 2015-03-10 08:37:39 UTC

*** This bug has been marked as a duplicate of bug 28069 ***