Closed Bug 1596782 Opened 11 months ago Closed 8 months ago

browser_protections_UI.js disabled on fission

Categories

(Firefox :: Protections UI, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED
Fission Milestone M4.1

People

(Reporter: enndeakin, Unassigned)

References

(Blocks 1 open bug)

Details

The test will load an out-of-process iframe.

This fails because the check at:

https://searchfox.org/mozilla-central/rev/cac340f10816707e91c46db6d285f80259420f07/dom/base/nsGlobalWindowOuter.cpp#5597

fails because the document uri here is about:blank and not the tracking page as it is in non-fission.

One probable cause is that UrlClassifierCommon::NotifyChannelBlocked tries to get the top window and this won't be the expected window in fission mode.

Depends on: etp-fission

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?
Fission Milestone: ? → M4.1

Erica, this bug is a blocker for Fission's current milestone (M4.1 aka "fix all the mochitests"), but it's currently unassigned. The Fission team is hoping teams will fix their mochitests for Fission before the end of Q1 (75 or 76 Nightly).

Will your team be able to prioritize this bug for Q1? If you don't think this mochitest failure should block shipping Fission, just let me know.

If you have questions for Fission engineers, you can reach them in the #fission channel on Slack or Riot.

Flags: needinfo?(ewright)

Bug 1599043 appears to have re-enabled this test already.

Status: NEW → RESOLVED
Closed: 8 months ago
Flags: needinfo?(ewright)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.