On Jan 17, 2:34 am, Sky <[email protected]> wrote: > The following is a bug that only occurs in Chrome and therefore may be > a Chrome bug and not a GWT bug. > > If I create a FocusPanel and place a TextBox inside it, it takes > several (more than 4) mouse clicks on the TextBox to give focus to the > TextBox so you can start typing. This problem does not exist in IE nor > FF. > > This is easily reproducible. I created a new blank project and simply > put a TextBox inside a FocusPanel. > > I want to find a workaround. If anyone can help me find one, that > would be great! > > I currently do not know what is causing the problem, but I am curious > as to the existence of the <input type="text"> that is created as the > first inner child of all FocusPanel divs. I do not understand why that > is necessary. Any DIV can have the key events, mouse events and focus > events added to them, so why is that invisible input needed? > > I am thinking of writing my own version of the FocusPanel, but I'm not > going to do that right away.
It looks like issue 1471 which will be fixed in the upcoming GWT 2.0.1 release: http://code.google.com/p/google-web-toolkit/issues/detail?id=1471 The workaround for now (accesskeys won't work though, and the FocusPanel won't be focusable in Safari 3) is to add the following to your gwt.xml: <replace-with name='com.google.gwt.user.client.ui.impl.FocusImpl'> <when-type-is name='com.google.gwt.user.client.ui.impl.FocusImpl' /> <when-property-is name='user.agent' value='safari' /> </replace-with>
-- 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.
