I frequently use native .onmouseover/.onmouseout events in my animations, and I always try to follow some limitations, which can save me from a set of known unpredictable behaviours concerning this matter. First of all, defer all your handlers attachments as much, as you're sure, that calling a constructor will already have the correct getAbsoluteLeft() method call results at this point. Second thing is that, when you process these two events to enable/disable some UI effects for smoothness purposes have some default pauses to determine whether it's still necessary to call the mirrored animation, or it was just a micro-break like one, when you move a mouse from one element of <ul> list to another, while this list is attached to the listened DOM element. Also think about using Cell<...> objects as a possible substitutions for old-school Widget ones.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/hogg6m8hWHoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
