I'm experiencing some problems when debugging (especially) static methods in super-dev-mode in Chrome. When I have inspected / unfolded the this-node in the scope variables view on a previous breakpoint the devtools-window begins to hang when entering a breakpoint in a static method. Chrome automatically unfolds the static method's this-node which seems to be the window-node. The scope variables view is filled with a huge number (all?) of functions. Obviously too much for the devtools.
Would it be possible to enclose those methods in an additional subnode / container variable to avoid the performance problem? Besides the problem for static methods it would also help with "normal" inspecting the window namespace. Correct me if I'm wrong, but one doesn't need those functions for debugging purposes.
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 firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.