Closed Bug 1610572 Opened 6 years ago Closed 6 years ago

Disable Feature Policy for FF73

Categories

(Core :: DOM: Security, defect, P1)

defect

Tracking

()

VERIFIED FIXED
mozilla74
Root Cause Product Decision
Tracking Status
firefox73 blocking verified
firefox74 --- fixed

People

(Reporter: ckerschb, Assigned: johannh)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-active])

Attachments

(2 files)

Given the regression of Bug 1609973 we should just disable FP for FF73 and re-evaluate what to do for FF74.

Depends on: 1609973
Severity: normal → critical
Priority: -- → P1
Assignee: nobody → ckerschb
Status: NEW → ASSIGNED
Whiteboard: [domsecurity-active]
Attachment #9122322 - Attachment description: Bug 1610572: Disable Feature Policy for FF73. r=johann → Bug 1610572: Disable Feature Policy for FF73. r=johannh

Comment on attachment 9122322 [details]
Bug 1610572: Disable Feature Policy for FF73. r=johannh

Beta/Release Uplift Approval Request

  • User impact if declined: We recently regressed Feature Policy (e.g. within Bug 1609973) and are worried to face similar regressions. After careful considerations (Thomas, Johann, ckerschb) we decided to postpone shipping Feature Policy by one release. For now we are going to disable FP in FF73 and then re-evaluate what to do for FF74 soon.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The risk is low because we haven't yet shipped Feature Policy. We are going to pref it off.
  • String changes made/needed: no
Attachment #9122322 - Flags: approval-mozilla-beta?
Pushed by dvarga@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9885dcdec5c0 Disable Feature Policy for FF73. r=johannh

Comment on attachment 9122322 [details]
Bug 1610572: Disable Feature Policy for FF73. r=johannh

Disables Feature Policy for Fx73. Approved for 73.0b9.

Attachment #9122322 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74

From bug 1609973 comment 12 it looks like comment 5 disables feature policy for 73 release but not 73 beta. Shouldn't we be beta-testing this?

Flags: needinfo?(jhofmann)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

You mean shouldn't we be Beta testing the disabling? I'm not sure there's any point to doing that now that we'll be in late beta soon anyway. We've always operated under the assumption that you can just pref-off things last minute and they'd continue to work then, which I agree is a bit of a risk, but, either way, that's the system.

Flags: needinfo?(jhofmann)

Why was this reopened?

Flags: needinfo?(jcristau)

See bug 1609973 comment 15. The patch that landed here didn't touch firefox.js.

Flags: needinfo?(jcristau) → needinfo?(jhofmann)
Assignee: ckerschb → jhofmann
Status: REOPENED → ASSIGNED
Flags: needinfo?(jhofmann)

This pref was only defined in firefox.js in Beta, so it wasn't considered in the disable patch for Nightly.
Seems like we can safely remove it as it was always unnecessary.

Comment on attachment 9124068 [details]
Bug 1610572 - Only for Beta uplift - Remove feature policy pref in firefox.js. r=ckerschb

Follow-up fix to the already-approved patch. Approved for 73.0RC1.

Attachment #9124068 - Flags: approval-mozilla-release+
Flags: qe-verify+
Status: ASSIGNED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED

Bug 1603674 removed the duplication in 74.

QA Whiteboard: [qa-triaged]

Hello! Reproduced the issue with Firefox 73.0b11 (20200128001646) on Windows 10x64, using STR from 1609973#c0. Also dom.security.featurePolicy.enabled pref was set on true on 73.0b11.
Verified fixed with Firefox 73.0RC1 (20200203203546) on Windows 10x64, macOS 10.15 and Ubuntu 18.04. The dom.security.featurePolicy.enabled pref is set on false.

Status: RESOLVED → VERIFIED
Flags: qe-verify+

Please specify a root cause for this bug. See :tmaity for more information.

Root Cause: --- → ?
Root Cause: ? → Product Decision
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: