- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 May 2013 17:29:32 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21067 --- Comment #17 from Steve Orvell <sorvell@chromium.org> --- event.path solves the use cases outlined in the bug where it was requested: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21066. In that thread, it was noted that insertionParent does not provide enough information to construct the event.path. If there is a general need to be able to construct the composed ancestor tree by traversing up from a given node, insertionParent is insufficient for that purpose for the same reason. See, for example, https://www.w3.org/Bugs/Public/show_bug.cgi?id=21066#c16. It seems to me that reprojection makes insertionParent not a useful concept and we should remove it and address general 'traversing up the composed tree' via some alternate api, if necessary. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 17 May 2013 17:29:38 UTC