We don't use GXT, but we have similar intermittent selenium test failures with the same message: "openedWindow has no properties". These have only started appearing after we updated to GWT 1.5. I've isolated this to an rpc call that happens as the result of a click, since other rpc calls seem to work fine (those that happen onModuleLoad for example).
This error occurs inside the selenium wrapper for window.open. I'm still trying to find a root cause but it seems strange that a window.open would be triggered during this rpc call. Also, looking at other selenium posts for this message seems to indicate that this happens when the firefox being driven by selenium has the popup blocker enabled, but we get the same error with it disabled. On Jul 21, 12:11 pm, David <[EMAIL PROTECTED]> wrote: > I have some Selenium tests that were working under mygwt/Gwt 1.4 that > are now broken with the only change being to upgrade to GXT 1.0 and > GWT 1.5RC1. I am getting a (TypeError): openedWindow has no > properties > fileName:http://localhost:8080/selenium-server/core/scripts/selenium-browserbo... > lineNumber: 557 > > This is occuring during a GWT RPC call. It appears the failure > happens Anybody here have selenium tests working with GXT1.0 using > GWT's RPC calls? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
