New wpt crashes in /html/semantics/embedded-content/the-iframe-element/ [sandbox-top-navigation-child.tentative.sub.window.html, sandbox-top-navigation-escalate-privileges.tentative.sub.window.html, and 1 others]
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
Details
(Whiteboard: [wpt])
Syncing wpt PR 43984 found new crashes in CI
Affected Tests
- /html/semantics/embedded-content/the-iframe-element/sandbox-top-navigation-child.tentative.sub.window.html [wpt.fyi]:
CRASH - /html/semantics/embedded-content/the-iframe-element/sandbox-top-navigation-escalate-privileges.tentative.sub.window.html [wpt.fyi]:
CRASH - /html/semantics/embedded-content/the-iframe-element/sandbox-top-navigation-grandchild.tentative.sub.window.html [wpt.fyi]:
CRASH
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
Getting the crash signature into these bug reports is a TODO; sorry
These updates will be on mozilla-central once bug 1874526 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
|
||
Comment 1•2 years ago
|
||
If I run the test locally or look at a log with the crash on treeherder (e.g. in bug 1876001), it appears that the CRASH here is from an unwanted/unexpected remote connection being opened to google.com.
That likely comes from this line:
https://searchfox.org/mozilla-central/rev/9cd4ea81e27db6b767f1d9bbbcf47da238dd64fa/testing/web-platform/tests/html/semantics/embedded-content/the-iframe-element/resources/sandbox-top-navigation-helper.js#41
window.top.location.href = "https://google.com";
|
|
||
Comment 2•2 years ago
|
||
I posted a heads-up to the test author at https://github.com/web-platform-tests/wpt/pull/35697#issuecomment-1970026245 . In the meantime, I think we can work around this locally by resolving google.com to localhost by setting network.dns.native-is-localhost to true for these tests, as Valentin suggested for a related issue over in bug 1876001 comment 10.
|
||
Comment 3•1 year ago
|
||
WPT was fixed.
Description
•