Hi Pradeep! Thanks for your postings. It was interesting to learn about things changed with the new Selenium 1.0b version. I'm not sure yet how to go about the new version with regard to qooxdoo. Obviously, some of the internals have changed from 0.9, so we might have to support two versions in the user extension. For the time being, I would postpone any modifications related to 1.0 until a stable version has been release.
I have opened a bug report (bug#1418) so your information is not lost. You might want to add comments to this bug, or vote for it. Cheers, Thomas > Hi, > > I found the issue for the problem. One correction is that, the window > object was not a URL but a window object wrapped by XPCNativeWrapper. The > XPCNativeWrapper is for security purposes which avoids exposing the > javascript objects of the actual object (hides them). With the latest > Selenium IDE, this is what is happening. Prior to this, it was the actual > window object in which we can access the qx object directly by using > inWindow.qx. > > To overcome this issue, I am using the wrappedJSObject in > XPCNativeWrapper window object. I am accessing the qx object by using > inWindow.wrappedJSObject.qx which works. I updated the user extension by > replacing inWindow.qx to inWindow.wrappedJSObject.qx. > > I am not sure how good a solution is this but it solves my problem. I am > posting this because anyone facing the same issue can easily fix it. > > Also, please let me know if there are any other better solution. > > Thanks, > Pradeep K R > > > > Pradeep wrote: > >> Hi, >> >> I was using the qx locator in Selenium IDE 0.8.7 for identifying the >> Qooxdoo elements. I was using Firefox 2.0 then. It was working fine. >> >> But, when I installed Firefox 3.0, I need to update the Selenium IDE as >> well to 1.0b2. But now, when I use the qx locator, it is not working. It >> is throwing the following error >> [error] locator not found: qx=Login, error = Error: Element qx=Login >> not found >> >> I tried debugging it and found that the Window object getting passed in >> the locateElementByQx method has changed. Now, it is coming as a URL and >> when it tries to do a inWindow.qx, it fails. Earlier, I used to get the >> actual window object which has qx residing in it. >> >> Am I doing something wrong with the new Selenium IDE. I am using the >> new user extension only. >> >> Please help me... >> >> Thanks, >> Pradeep K R >> >> > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
