WPTs for framebusting fail in WPT repo
Categories
(Core :: DOM: Security, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox145 | --- | wontfix |
| firefox146 | --- | wontfix |
| firefox147 | --- | wontfix |
| firefox148 | --- | fix-optional |
People
(Reporter: maltejur, Assigned: maltejur)
References
(Depends on 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
The tentative web platform tests added with Bug 1419501 to test our framebusting intervention currently only pass in mozilla-central and not in the WPT repository on GitHub. This is because our framebusting implementation is only active if dom.disable_open_during_load (pop-up blocking) is enabled, and that pref generally gets disabled in automation builds. In mozilla-central, we work around this by manually disabling dom.disable_open_during_load again for the individual tests. Setting individual prefs is not possible, though, in the main WPT GitHub repository outside mozilla-central.
| Assignee | ||
Comment 1•2 months ago
|
||
With Bug 2001668, manually enabling pop-up blocking via pref for these
individual WPTs is no longer required.
| Assignee | ||
Comment 2•2 months ago
|
||
The assumption in these tests previously was, that, contrary to the rest of the
WPTs, they should be run with pop-up blocking enabled. This is no longer the
case, so these manual user activations to prevent pop-ups from being blocked can
be removed.
Comment 3•2 months ago
|
||
Set release status flags based on info from the regressing bug 1419501
Updated•2 months ago
|
Comment 4•2 months ago
|
||
Set release status flags based on info from the regressing bug 1419501
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 5•1 month ago
|
||
The severity field is not set for this bug.
:freddy, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Description
•