Probably not related but hit a weird issue with FF20 too: * undefined in a variable that the Java source (compiled to JS) says should be initialised. * works fine in all other browsers. * works in FF if firebug or the built in debugger turned on...
It was in some Request Factory code... we managed to trim what we were sending and the problem went away (not very comforting though). On Friday, April 5, 2013 9:49:20 PM UTC+1, Geoffrey Wiseman wrote: > > I hit an issue this afternoon where I have an unexplained issue with a > select where I can't select any of the options in it, and it seems like the > handler isn't even being called (or isn't triggering the debugger in > Eclipse, anyway), in either dev mode or after deployment in regular browser > usage (including in FF safe mode, which disables all the plugins). This is > true in FF20, but not in FF19. > > It's only one select out of many in our application, so there are clearly > complicating circumstances, it's not just "select controls don't work in > FF20/GWT", but it's odd to me that it works in FF19 and doesn't work in > FF20. Since I don't have any idea of the cause yet, I'm not sounding > alarms, but I thought I'd put a placeholder in here in case anyone else is > experiencing a FF19/FF20 regression and is farther along in their analysis > than I am. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
