qqilihq
January 15, 2019, 1:03pm
34
I’m currently overwhelmed with work, so I didn’t have time to look at the WF or the site in detail. But, what catches my eye:
html/body/div[1]/div[4]/div[1]/div/div[1]/div[2]/div/div[2]/div[1]/div[2]/div/div/div[2]/div/iframe
Obviously, the page you’re working with contains <iframe>s. In case you want to access elements within an <iframe>, you need to explicitly switch to this iframe first. We have actually discussed this a while ago in the following thread:
The reason is, that the content in the login window is shown within an <iframe>, and Find Elements will not operate into the <iframe>:
[02]
What you’ll have to do after opening the login window:
Get the <iframe> using a Find Elements node (use e.g. an ID query iframe_login, or XPath //*[@id='iframe_login'])
Use the Frame node, check ‘WebElement’ and select the <iframe> column from previous step
Continue with your existing workflow
In case you need to ‘escape’ from the <iframe> late…
– Philipp
1 Like