For anyone still (*sigh*) dependent on GWT 1.4, the removal of the isSameNode function in Firefox 10 will likely result in JavaScript errors in your compiled modules.
https://bugzilla.mozilla.org/show_bug.cgi?id=687400 https://developer.mozilla.org/en/Firefox_10_for_developers https://developer.mozilla.org/en/DOM/Node.isSameNode This is a similar situation to the removal of getBoxObjectFor in Firefox 3.6: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/88a8437754345092/e519ad6f11a081ad The problem can be fixed by editing DOMImplMozilla.java in gwt- user.jar and replacing the 4 isSameNode tests with === comparisons. The comments indicate that isSameNode was used because direct comparison was unreliable, but presumably this is no longer an issue in later versions of Firefox. If you need to support a wide range of Firefox versions, then testing for the existence of the function and using it if it exists or falling back to direct comparison if it doesn't is probably the safest approach. DOMImplMozilla.java is the only file you need to modify. The corresponding .class file is not used for compilation or in hosted mode, and gwt-servlet.jar does not include this class. -- 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.
