Skip to content

Fix iframe strict mode violation in E2E tests#120

Closed
mraible wants to merge 3 commits intomainfrom
fix-iframe-strict-mode
Closed

Fix iframe strict mode violation in E2E tests#120
mraible wants to merge 3 commits intomainfrom
fix-iframe-strict-mode

Conversation

@mraible
Copy link
Copy Markdown
Contributor

@mraible mraible commented Apr 7, 2026

The Falcon console sometimes renders a hidden iframe alongside the app extension iframe, causing Playwright's strict mode to fail with "resolved to 2 elements" when using locator('iframe'). Adding .first() targets the first (visible) iframe and avoids the error.

This was causing nightly E2E test failures in CI.

mraible added 3 commits April 6, 2026 11:30
Add overrides to resolve known vulnerabilities:
- picomatch@2 -> 2.3.2 (ReDoS via extglob quantifiers)
- picomatch@4 -> 4.0.4 (ReDoS via extglob quantifiers)
- yaml@1 -> 1.10.3 (stack overflow via deeply nested collections)
- brace-expansion@2 -> 2.0.3 (zero-step sequence hang)
- lodash -> 4.18.1 (prototype pollution and code injection)

Remaining: brace-expansion 1.x (1.1.12) has no fixed version available.
The Falcon console sometimes renders a hidden iframe alongside the app
extension iframe. Using locator('iframe') fails with "strict mode
violation: resolved to 2 elements". Adding .first() targets the visible
iframe and avoids the error.
@mraible mraible requested a review from a team April 7, 2026 16:00
@mraible
Copy link
Copy Markdown
Contributor Author

mraible commented Apr 7, 2026

Closing - the iframe failure was a one-time transient issue, not a recurring bug. Extension apps have been passing consistently on prior nights.

@mraible mraible closed this Apr 7, 2026
@mraible mraible deleted the fix-iframe-strict-mode branch April 7, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant