- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Apr 2013 03:33:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21404 --- Comment #9 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to comment #8) > I guess that since element.addEventListener's third parameter, useCapture, > is 'false' in default, people is likely to have a mental model of 'event > listernes are called from inner to outer'. > That might support the idea of 'minicing bubbling events' for AT_TARGET > phase. Right. Most of the time this parameter is false (very few use capture), so the order of events looks whacky: first listener is fired on the host that's farthest from the target. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 1 April 2013 03:33:16 UTC