FIXED! GWT 2.0.1 fixed all of these issues!!! I am so incredibly happy! Well done, GWT team! Pat on the back! Good job!
I hope you (GWT development team) feel appreciated for your hard work! cheers! On Feb 1, 7:04 pm, Sky <[email protected]> wrote: > Wow! Now another FocusPanel's MouseDown event doesn't even fire! > Except I can make it fire if I do the following. When I click on this > element (object B) another element (object A) is losing focus, so if I > put a breakpoint in the onBlur event on that item (object A), then > when I click on the other item (object B) Eclipse breaks into that > code, I hit F8 to continue and what do you know, the MouseDown event > actually fires and everything runs. Do you understand? The MouseDown > event on object B ONLY fires if I have a breakpoint in OnBlur event > for object A! > > These problems are ONLY in chrome. All other browsers act as expected. > > I can't possibly fix something like this. Can anyone help me? These > problems must be a GWT bug(s). > > I'm using GWT 2.0.0, the latest Eclipse, Stable channel of Chrome. > > On Feb 1, 6:15 pm, Sky <[email protected]> wrote: > > > > > I click on my FocusPanel and before MouseUp event fires, but after > > MouseDown event, the Blur event is fired, which is very much > > undesired. > > > This only happens in Chrome, so it may be a Chrome bug. It does not > > happen in FF and IE. > > > It may be my fault, but I am not explicitly setting focus on any > > elements in my MouseDown code. I do set other aspects of other > > elements, like visibility. > > > Has anyone else experienced something like this before? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
