For anyone that's interested, the problem is solved by using the correct document object. I started by using elem.ownerDocument instead of document. However, I've found some gwt-docs that say you should use $doc instead of document.
On Mar 20, 2:49 pm, johnpearcey <[email protected]> wrote: > This looks a little like a GWT compiler bug but I'm not sure. All > methods that manipulate a DOM node fail in IE6 where native script > calls are made. They work fine in Firefox and hosted mode. I am > obtaining scripts from a database and running it using eval(). At > first I suspected a compiler optimisation bug but have since found > that a more straightforward call will not work on IE6. For example: > > public static native void eval_js( Node elem, String evalCode )/*-{ > elem.appendChild( document.createTextNode(Math.random()) ); > > }-*/; > > Under IE6, catching the exception in GWT gives the following > information: > > (Error): Invalid argument. number -2147024809 description: Invalid > argument. > > Firefox and GWT hosted mode both work fine. The node concerned is > correctly attached both physically and logically. It seems that any > attempt to break into native script calls give the same problem. > Interestingly enough the following call works fine: > alert( elem.nodeType ); > > It seems as if the node is read-only??? > > Has anyone experienced this? I've been working one this for two days > now and have run out of work-around ideas. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
