- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 May 2013 17:15:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21067 --- Comment #16 from Elliott Sprehn <esprehn@gmail.com> --- (In reply to comment #15) > ... > > Okay. I will wait to add insertionParent to the spec until webdevs (Polymer > teams and others) have concluded that event.path is not enough. > > If that happens, I think we need to go back to re-evaluate the opportunities > for a better solution (and maybe even nix event.path in the process). As a webdev, event path is not enough. It doesn't address Google Feedback's use case of wanting to walk up the ancestor chain to figure out containing blocks, event.path would require dispatching fake events on every node and is crazy expensive (and does rewriting and other magic). It also doesn't allow positioning an object easily, since you have no trivial way to walk up the tree and decide who your positioned ancestor is without dispatching fake events... -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 17 May 2013 17:15:20 UTC