I just have a question regarding an application that BOT will be dealing with if is built underlying on iFrame, will it add to the complexity to the BOT to identify selectors ? OR, it’s just an application that BOT could easily identity selectors and work with ?
Whats your experience working with applications built underlying on iFrame ?
We do try to improve iframe automation. Also, I’ve seen a cleaver solution of one user. He would extract the url of the iframe, append it to the main url of the page and then open such prepared link in the new tab. This would allow him to have full access to the elements of that iframe
I encountered same issue and for me works following:
Getting data from iframe works only with packages Uipath.UIAutomation.Activities version 18.4.6 and only without using Attach Browser activities as with version 18.4.6 studio doesnt know Edge Browser type and with IE type its of course not working. It was working for me with full selectors.
‚Edge‘ browser type is known only for version 19.x but then its not able to retrieve data from iframe.
Are there any plans for UiPath to add this as an activity? Something like ‘Attach Iframe Scope’ that can be used within a Browser scope to allow interaction with the IFrame DOM? Retrieving the IFrame src attribute and opening it in a new tab is a good workaround, but if the IFrame interacts with the parent page at all it wouldn’t be a viable solution.
yes, I tried 19.7.0 uiautomation package version (using 2018.4.6 studio) and I was not able to search for each element within the iframe. Retrieving the url didnt work for me and using screen scraping methods didnt provide accurate data. Get text from iframe returns empty string.
When I instal 18.4.5 or 18.4.6 uiautomation package, its searching for each element also within the iframe and its possible to get text from these elements.
It would be nice to debug the issue. Would it be possible to receive some examples of the iframe that you are trying to access? Maybe a project that reproduces the issue using some publicly available website as an example?
We could then be able to investigate and fix the issue.
Wen using UiPath automation activities with the browser do not forget to switch to ‘Active Accessibility’ UI Framework. This will allow you to access iframes and their content.
You could do this by pressing ‘F4’ hotkey during selector selection or by pressing ‘UI Framework’ in UI Explorer
Thanks @loginerror. I tested to update to the preview version and Select Item with AA seems to work fine in Classic mode also, except for a visual bug. After the bot have selected “Opel”, I need to switch to another Chrome tab and back before the text is changed from “Volvo” to “Opel”.