- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 Apr 2012 10:21:40 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16176 --- Comment #8 from Hayato Ito <hayato@chromium.org> 2012-04-06 10:21:38 UTC --- I've spent some time on how event dispatching should behave if light children are distributed. Take a look at the attached image for example DOM tree and its composed shadow tree. https://www.w3.org/Bugs/Public/attachment.cgi?id=1108 Suppose a mouse moves from '#F' (relatedTarget) to '#D' (target). In this case, on which nodes a 'mouseover' event should happen? My initial thought in this case is: - #D (target = #D, relatedTarget = #L) - #C (target = #D, relatedTarget = #L) - #J (target = #J, relatedTarget = #L) (This might be controversial, but I think an event should be fired on #J also) - ... (#G should be skipped...) - #B (target = #D, relatedTarget = #F) - #A (target = #D, relatedTarget = #F) This is one of ideas. If we try to keep compatibility as much as possible. That should be: - #D (target = #D, relatedTarget = #F (not #L)) - #C (target = #D, relatedTarget = #F (not #L)) - #J (target = #J, relatedTarget = #L) - ... (#G should be skipped...) - #B (target = #D, relatedTarget = #F) - #A (target = #D, relatedTarget = #F) I am afraid that this will make the situation (and the spec) complex, but I'd like to discuss what is expected and reasonable behavior. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 6 April 2012 10:21:42 UTC