Re: How can I add a MouseOutHandler to a FlexTable cell?

2009-06-12 Thread matthew jones
Try this instead. addMouseOverHandler(MouseOverHandler handler) { return addDomHandler(handler, MouseOverEvent.getType()); } On Jun 12, 12:52 pm, Eduardo Nunes esnu...@gmail.com wrote: Well, the subject says everything, I would like to know how can I add a MouseOutHandler

Seeing RangeError: Maximum call stack size exceeded. with Safari 5 and our GWT 2.0.3 app

2010-06-08 Thread matthew jones
Anyone else having this issue? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to

Re: Safari 5 / GWT / GWT EXT 2.0.6

2010-06-08 Thread matthew jones
Same thing here. On Jun 8, 11:43 am, eric73 e...@pentila.com wrote: Hi all! today I upgrade my Safari 4.0 to Safari 5.0 on Snow (other browsers are OK) Now my sites build with GWT 2.0.3 / GWT EXT 2.0.6 etc ... sometime don't run. I test its with Safari 4.0 and all worked. A javascript

Re: Safari 5 / GWT / GWT EXT 2.0.6

2010-06-08 Thread matthew jones
We're using deferred commands and code splitting. On Jun 8, 12:12 pm, eric73 e...@pentila.com wrote: On 8 juin, 18:54, Jeff Chimene jchim...@gmail.com wrote: On 06/08/2010 09:46 AM, matthew jones wrote: Same thing here. On Jun 8, 11:43 am, eric73 e...@pentila.com wrote: Hi all

Re: Safari 5 / GWT / GWT EXT 2.0.6

2010-06-09 Thread matthew jones
mode then I'm seeing the exception again. On Jun 8, 1:22 pm, eric73 e...@pentila.com wrote: I am not use deferred commands and code splitting so the problem stay unsolved . Please help On 8 juin, 19:17, matthew jones bigboxe...@gmail.com wrote: We're using deferred commands and code

Re: Safari 5 - (RangeError): Maximum call stack size exceeded

2010-06-09 Thread matthew jones
It seems to be 32bit safari related... running in rosetta or on SL in 64bit clears the issue up for us. On Jun 9, 10:11 am, Pascal zig...@gmail.com wrote: When we try to run dev mode to get a better stack trace, everything works fine. Could it be a change in the javascript engine in safari 5