Sounds strange. You can open Chrome Dev Tools and on the sources tab there is a small "pause" icon on the right which says "Pause on exceptions". You can even tell Chrome to pause on any exception regardless if caught or not. So you could start your app and before clicking the tab that does not work you could activate that Chrome feature to see if any exception is thrown that might not reach the browser console for any reason.
Alternatively you could set a break point in Chrome debugger and then step through your code until it might fails. You could also place a GWT.debugger() call into your Java code and Chrome will stop at that location just like with break points. Also as a general hint: If you use GWT 2.7. then the bookmarklets are generally not needed. When you launch the SuperDevMode CodeServer it will generate a special <modulename>.nocache.js file that triggers recompilation whenever you reload the browser. However I think GWT 2.7 has a timestamp bug and if that <modulename>.nocache.js file already exists because you have done some normal compilation then it might happen that the CodeServer does not replace that file. So to be sure you can delete the GWT output folder, restart SDM and then deploy the app with the newly generated <modulename>.nocache.js. -- J. -- 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. For more options, visit https://groups.google.com/d/optout.
