Need to automate Iframe elements via the WebDriver in Ranorex
As of know we are unable to automate the IFrame objects using web driver. it will be good if the IFrame objects are also part of web driver integration
The status of this idea seems to be out of date, sorry for that.
Released with Ranorex 8.1:
Added SwitchToFrame and SwitchToParentFrame actions for WebDriverDocumentFlavorElement to ease frame navigation.
Please find the release notes here: https://www.ranorex.com/release-notes/
Please let us know if you have any question or additional requests on that.
Ranorex Product Management Team
Sunil Dahiya commented
Not only on web, the same issue is applicable for the Mobile apps. Developers are using iframes in Apps and therefore the objects inside iframes are not identifiable.
We are having the same issues working in our projects, please we need a solution asap
Tjardan Broekema commented
In my opinion this is a bug or oversight and should not be a feature at all. Expanding the Selenium API's to be able to switch to iFrame context could be a first implementation as a temporary workaround. But I agree with Aracknid this should just work out of the box.
[Deleted User] commented
Please add this to Ranorex, as for now I am not able to automate registration processes for certain email providers. This is a huge blocker to me.
Bernhard Kaszt commented
In our product, everything is also nested inside frames and iframes. Without native support of Frames in Ranorex, the webdriver integration is pretty much useless. Therefore I also consider this as a bug.
Richard Brew commented
I also need to be able to find objects within Frames and iFrames as the site I am testing has everything buried within frames and I cannot use the WebDriver.
This doesn't have a lot of votes, but in my opinion this is a bug that needs to be fixed. Your PR department was going on and on about how the new webdriver implementation was great and wonderful, but as soon as you actually try to run a script that needs to find an element in an Iframe, suddenly it cannot find the element you are looking for and we find out that more 'selenium' code needs to be added for it to work because of the way selenium expects users to switch to the iframes. Guess what... I'm not a selenium developer and I didn't really want to spend a ton of time trying to get everything working just so I could test Edge. You guys need to do this automatically for us just like Ranorex does. Maybe simple web pages don't have many iframes, but an application hosted on the web has many of them.