- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Aug 2013 20:05:42 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22141 Erik Arvidsson <arv@chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arv@chromium.org --- Comment #3 from Erik Arvidsson <arv@chromium.org> --- I think this is the wrong solution. `contains` has always meant that I can walk from the node's parentNode to the ancestor. This changes the semantics of contains. What is the scenario we are trying to solve? Figuring that out, we can then come up with a reasonable API without changing the semantics of existing methods. Let me flip the coin a bit. I've been using contains as a signal that the node is not in the main document (in a shadow tree or a disconnected tree). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 1 August 2013 20:05:46 UTC