On Tue, Dec 27, 2011 at 5:27 PM, <[email protected]> wrote: > I have posted a comment on Issue 537 which raised this problem almost a year > ago but never produced any clear resolution. The link is: > > http://code.google.com/p/pyjamas/issues/detail?id=537&start=100 > > My conclusion, of course based only on my own applications, is that setFocus > would work properly in Chrome/Safari if we just threw this override away. > Since it's easy to check, it would be nice if people would try that on their > bleeding edge applications. Or perhaps somebody actually knows of a good > reason why there needs to be an override and can make it work correctly.
phil, if you check GWT's latest code, it's best to always follow that. i've seen circumstances where not having the override did some pretty strange things. l.

