- From: <bugzilla@jessica.w3.org>
- Date: Fri, 21 Mar 2014 22:19:31 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #52 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to Boris Zbarsky from comment #50) Thanks for the test case -- I turned it into a jsbin: http://jsbin.com/newir/1/edit > What I don't quite understand, if we posit that we do want to put all the > insertion points in the path, is why the path is not the somewhat more > intuitive: > > 3,2,10,9,8,7,6,5,4,1 Here's how the reasoning works. Since insertion points aren't in the composed tree, but are in event path, we have to come up with a mental model of how they are added. Here's the mental model that the spec ascribes: During distribution, first 2 is distributed into insertion point 7. So the path is now 3,2,7. Then, the result of that distributed into 10, so the path is now 3,2,7,10. In other words, the spec follows the distribution sequence and builds the path accordingly. FWIW, I am fine for insertion points to not receive any events. I'll be sad about it for a day, and then I'll get over it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 21 March 2014 22:19:33 UTC