[fix]: preserve cross origin iframes after `act()`
Merged
SE
19d ago+123+123+012345678901234567890123456789-15-15-01234567890123456789
why
- calling
act()could prevent Stagehand from seeing and interacting with newly loaded cross-origin iframes because its network-settling helper overwrote the browser’s auto-attach configuration
what changed
- removed the conflicting auto-attach call, leaving attachment management to BrowserContext.
- added a regression test verifying that cross-origin iframes created after act() remain visible in snapshots and support subsequent actions.
Summary by cubic
Fixes an issue where calling act() could prevent Stagehand from seeing and interacting with newly loaded cross-origin iframes. The network-settling helper in actHandlerUtils.ts was overwriting the browser's auto-attach configuration, which broke attachment management owned by BrowserContext.
- Removed the conflicting
Target.setAutoAttachcall; BrowserContext now handles child-target attachment. - Added a regression test verifying cross-origin iframes created after
act()remain visible in snapshots and support subsequent actions.