Closed Bug 1596782 Opened 5 years ago Closed 5 years ago

browser_protections_UI.js disabled on fission


(Firefox :: Protections UI, task)

Not set



Fission Milestone M4.1


(Reporter: enndeakin, Unassigned)


(Blocks 1 open bug)


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

This fails because the check at:

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.

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:


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.

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