nested iframes and iframe name

[snak3b1te]

Hi,
I try to automate something in (irefox in) a horrible web UI that is dynamically nesting iframes within iframes. Plus, some have IDs while others only have names (<iframe name="some-name">).
I tried both CSS selectors and XPath.
I tried to #iframe_w_id |> [name="frame-name"], I tried to "switch frame" - one at a time and directly to the inner frame.

Are nested iframes supported at all?

The "switch-frame" block says it supports CSS and XPath. Other blocks have a drop-down which one it is, this one dosn't. Does it still support both selectors?

XPath seems to be evaluated only within the current frame, correct? At least running //iframe[@name='some-name'] or //input[@id="id-in-nested-iframe"] did not work,

Regarding the iframe selector extension to CSS selectors - is the meaning the left expression selects the iframe element and the right expression selects an element that is a direct child of the iframe? Is it more like elem1 elem2with elem2 is a descendant or more like elem1 > elem2 where elem1 is the parent of elem2, just with iframes?

Thanks.
Chris.

[snak3b1te]

I'm not comfy with my JS, but if I grep the code for |> a (the?) relevant potion appears to be in ./src/content/index.js in async function executeBlock(data){}. If I'm not mistaken, it checks for a single appearance of it and uses the left part to locate the frame and the right to select within the frame. There seems to be no check for further |> in the selector.

I would assume that the part (lines 79..91) should be moved into a function and recurse or looped until all |> are treated.

However, there is more in App.vue (and ~10 other locations) which is even more mysterious for me not being a JS affectionado. So, wouldn't dare to touch it myself :-|

Could someone look into this? And even implement? Would be awesome!
Chris.

[snak3b1te]

Some answers for reference:

• No, selecting nested (i)frames is not supported. See previous post for details.
• semantic is similar to elem1 elem2. I.e., the left part selects the frame. The right part is then applied to the (sub)document. Could be anywhere within.
• the switch-frame block will only prepend the selector to subsequent blocks. It does not really create a context. So, no dice for nesting.
• XPath vs CSS is determined by a regexp. The regexp tests something that looks.... odd. Cf. src/utils/helper.js (no, I have no better idea, might test for / but that's also no 100%)
• XPath is evaluated per document, i.e., does not include nested (i)frames
• interestingly enough, due to the way the switch-frame block works, you can have a mixed XPath / CSS selector, with left and right of |> independent of the other