[Bug 21976] [imports]: Preventing DOM hierarchy cycles

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

--- Comment #3 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #2)
> Can someone please explain this? I'd like to have this covered.

Rafael is probably the right guy to write a much clearer explanation, but I'll
try first :)

Suppose you have the following import structure:

index.html:
<link rel=import href=a.html id=i-a>
<link rel=import href=b.html id=i-b>

a.html:
<link rel=import href=b.html id=a-b>

b.html:
<link rel=import href=c.html id=b-c>

c.html:
<link rel=import href=a.html id=c-a>

If we suppose that only one import is loaded per URL (that's what the spec says
at the moment), b.html's parent imports are both index.html and a.html, which
creates the tree-shaped ancestry chain that Rafael mentions.

A naive fix would be to always load a different import for a URL, but now we
can't easily resolve cycles in the import tree. For example, when loading c,
it's unclear what to do with #c-a.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 16 August 2013 16:03:40 UTC