- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Apr 2013 02:37:02 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21404 --- Comment #4 from Hayato Ito <hayato@chromium.org> --- To continue further, let me confirm 'the desired behavior' at first. Given the event path, from Node A (top-most) to Node G (target, inner-most), where C and D are shadow hosts and G is the target, an event dispatching order in the current WebKit implementaion is: (T: AT_TARGET, C: CAPTURING, B: BUBBLING) For bubbling events: A 1 (C) 11 (B) B 2 (C) 10 (B) C (SH) 3 (T) D 4 (C) 9 (B) E (SH) 5 (T) F 6 (C) 8 (B) G (Target) 7 (T) For non-bubbling events: A 1 (C) B 2 (C) C (SH) 3 (T) D 4 (C) E (SH) 5 (T) F 6 (C) G (Target) 7 (T) Are we changing this behavior? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 1 April 2013 02:37:04 UTC