[Bug 20127] [Templates]: Template needs to disallow DOM hierarchy cycles which can result from template.contents from bugzilla@jessica.w3.org on 2013-01-25 (public-webapps-bugzilla@w3.org from January 2013)

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Jan 2013 13:58:18 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20127-2532-lVGCPfvErq@http.www.w3.org/Bugs/Public/>

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

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #3 from Anne <annevk@annevk.nl> ---
Lets keep this open until it's fixed then okay?

So it seems like in addition to checking the inclusive ancestors as is already
done by the pre-insert and replace algorithms, we also need to check the
inclusive ancestors of the object the tree is associated with.

Should we maybe introduce a new node that inherits from DocumentFragment that
can carry that additional semantic as well as provide a pointer to the hosting
element?

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

Received on Friday, 25 January 2013 13:58:31 UTC