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 28031 - Does the destination insertion points include Shadow IP without older trees?
Summary: Does the destination insertion points include Shadow IP without older trees?
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Koji Ishii
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 23887
  Show dependency treegraph
 
Reported: 2015-02-16 01:49 UTC by Koji Ishii
Modified: 2015-02-16 05:15 UTC (History)
9 users (show)

See Also:


Attachments

Description Koji Ishii 2015-02-16 01:49:26 UTC
From comment 150 of bug 23887.

Consider a tree:

A
  SR
    SIP
  B

The question is does B's "destination insertion points"[1] include the SIP?

The argument to include is that "3.3 Shadow Insertion Points"[2] defines such SIP as a valid shadow insertion points.

The argument not to include is that the definition of "destination insertion points" in "3.4 Distribution Results"[1] says:
> destination insertion points, which consists of insertion points to where the node is distributed

But the sentence looks a bit confusing regardless of this issue, because a node is distributed only to the final destination point, so the destination insertion points being a list of "node *is* distributed" looks inaccurate.

So two suggestions here:
1. Fix the 3.4 wording from "is" to "may be". It's inaccurate anyway.
2. Discuss whether such SIP should be included, and if we conclude not to, change the definition of "3.3 Shadow Insertion Points"[2].

Note that this issue can affect more than event path, such as Element.getDestinationInsertionPoints[3].

[1] http://w3c.github.io/webcomponents/spec/shadow/#dfn-destination-insertion-points
[2] http://w3c.github.io/webcomponents/spec/shadow/#shadow-insertion-points
[3] http://w3c.github.io/webcomponents/spec/shadow/#extensions-to-element-interface
Comment 1 Hayato Ito 2015-02-16 02:17:55 UTC
> But the sentence looks a bit confusing regardless of this issue, because a
> node is distributed only to the final destination point

I'm afraid that's the root cause of your confusing.
A node can be distributed to multiple insertion points. The final destination point is just one of that. I think the spec is clear for that.
Comment 2 Koji Ishii 2015-02-16 05:04:15 UTC
The final destination point is clear.

What's not clear to me is whether "destination insertion points" includes "a shadow insertion point without older shadow roots".

Such shadow insertion points are still valid according to the definition of shadow insertion points. However, since there's no older shadow roots, content will never be distributed to it.

Does "destination insertion points" include "a valid insertion point where content will never be distributed to"?
Comment 3 Koji Ishii 2015-02-16 05:15:14 UTC
Talked with Hayato and understood what I misunderstood. I thought content will never be distributed the shadow insertion point. Sorry for the trouble.