- From: <bugzilla@jessica.w3.org>
- Date: Tue, 17 Dec 2013 03:26:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #42 from Hayato Ito <hayato@chromium.org> --- My biggest concern about removing insertion point from the event path is whether it would cause developers a kind of *burden* or not. We need more feedbacks. > 1. all insertion points in event path. > 2. no insertion points in event path. > 3. last insertion point in event path. My understanding between (1) and (2) is: By (1): For each node tree: - For the document tree, the event path would be [child1, 1st SH, document] - For 1st shadow tree, the event path would be [IP1, 2nd SH, 1st SR] - For 2nd shadow tree, the event path would be [IP3, IP3's parent, 2nd SR] By (2): For each node tree: - For the document tree, the event path would be [child1, 1st SH, document] - For 1st shadow tree, the event path would be [2nd SH, 1st SR] - For 2nd shadow tree, the event path would be [IP3's parent, 2nd SR] Although I don't have a strong opinion whether which, (1) or (2) is better, I am still not convinced that (2) is much better than (1). So far, I think (1) is more useful for developers than (2). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 17 December 2013 03:26:56 UTC