Open aarondufall opened 3 months ago
any updates on this?
I tried to work on a pr, but wasn't successful
This issue was with the headless browser service we were using. They didn't have the same flags for Chrome that Ferrum uses by default. Once the flags were changed, this issue was solved.
The flag required for us was --disable-site-isolation-trials.
Describe the bug
When the browser finds an iframe in the DOM, it publishes a
Page.frameAttached event
, then Ferrum takes the params and uses them to create a Frame object that adds to a collection of frames on the current Page object. When the src URL for the iFrame contains a URL with a different host to the parent, it fires aPage.frameDetached
with reasonswap
. Then, aTarget.targetCreated
with type IFrame is published, followed by aTarget.targetInfoChanged
event. From what I can tell, looking at the Ferrum source code, it doesn't handle typeIFrame
.In the
contexts#subscribe
, all the event handlers have this line, causing typeIFrame
to be ignoredTo Reproduce Goto a page where the iframe src attribute has a different host to the main page.
Expected behavior Access the iframe using the target id in the collection of
Frame
objects on the mainPage
object