On Tue, 27 Dec 2011 17:53:52 +0000, lkcl luke <luke.leighton-AT-gmail.com> 
wrote:

> 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.

Luke,
    I have checked out the gwt code and it appears to me that that Safari 
override code has been commented out. I have posted the details in a further 
comment on Issue 537. I think I found the right place in gwt but I am not at 
all familiar with the way it is organised, so it would be helpful if someone 
who is more au fait with it would check my conclusion.

Phil

Reply via email to