Thomas Broyer has posted comments on this change.
Change subject: Fix for issue 1525
......................................................................
Patch Set 2:
Just wondering: the root issue is that you don't get mouseout events in
some conditions, and by capturing events you now get mouseout events *for
other elements* (which is why you removed the test about the event's target
being within the button, right?). Won't that possibly cause issues that
other elements don't see mouseout events either? (e.g. the button is inside
a panel that itself listens to mouseover and mouseout, when hovering
quickly across that panel, you enter the button which starts capturing
events, the mouseout event for the button –for whichever reason– is not
dispatched, but that's not a problem form the PoV of the button as it now
has the mouseout event of the panel; but then the panel won't receive its
mouseout event, so we're just moving the problem, right?)
Could we possibly use "event previewing" instead?
--
To view, visit https://gwt-review.googlesource.com/2922
To unsubscribe, visit https://gwt-review.googlesource.com/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I2d49cae5ce0f8b8248aa15347914a5cd8da95287
Gerrit-PatchSet: 2
Gerrit-Project: gwt
Gerrit-Branch: master
Gerrit-Owner: Hilbrand Bouwkamp <hilbr...@h72.nl>
Gerrit-Reviewer: Thomas Broyer <t.bro...@gmail.com>
Gerrit-HasComments: No
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
