javascript - GWT Application throws 'JavaScriptException' in IE only, stack trace has no helpful information -
my gwt application throwing javascriptexception @ point. issue occurs in internet explorer (both ie 8 , ie 8 running ie7 mode).
the stack trace follows:
com.google.gwt.core.client.javascriptexception: (error): invalid argument. number: -2147024809 description: invalid argument. com.google.gwt.dev.shell.browserchannelserver.invokejavascript(browserchannelserver.java:195) com.google.gwt.dev.shell.modulespaceoophm.doinvoke(modulespaceoophm.java:120) com.google.gwt.dev.shell.modulespace.invokenative(modulespace.java:507) com.google.gwt.dev.shell.modulespace.invokenativeobject(modulespace.java:264) com.google.gwt.dev.shell.javascripthost.invokenativeobject(javascripthost.java:91) com.google.gwt.core.client.impl.impl.apply(impl.java) com.google.gwt.core.client.impl.impl.entry0(impl.java:188) sun.reflect.generatedmethodaccessor51.invoke(unknown source) sun.reflect.delegatingmethodaccessorimpl.invoke(unknown source) java.lang.reflect.method.invoke(unknown source) com.google.gwt.dev.shell.methodadaptor.invoke(methodadaptor.java:103) com.google.gwt.dev.shell.methoddispatch.invoke(methoddispatch.java:71) com.google.gwt.dev.shell.oophmsessionhandler.invoke(oophmsessionhandler.java:157) com.google.gwt.dev.shell.browserchannel.reacttomessages(browserchannel.java:1668) com.google.gwt.dev.shell.browserchannelserver.processconnection(browserchannelserver.java:401) com.google.gwt.dev.shell.browserchannelserver.run(browserchannelserver.java:222) java.lang.thread.run(unknown source)
debugging has been impossible least. google has told me property being set improperly (ie bad character setwidth("190px!")
) or setting width 0px or else altogether.
since issue shows in ie, i've tried using ie developer tools debug, have come nothing.
how can go debugging properly?
this happened me , it's quite nightmare. proper usage of git/svn/cvs whatever saves here situation really, getting point "where worked" great. can now:
- temporarily rid of custom css , see happens (leave plain default css gwt)
- debug on external server, it's not slow then
- try reproduce "certain point" , comment out related lines
- inspect generated site (some firebug-like tool ie, hope such thing exists)
- as suggested above, use pretty/detailed output style
- reading generated javascript gwt never solved problem :( css related stuff or custom usage of dom gwt
- get folks (or yourself) test various browsers on regular basis, it's nobrainer
Comments
Post a Comment