1936532 - Disable USER_RESTRICTED by default for content process in Beta and Release for Fx134.

Status: RESOLVED FIXED

(Core :: Security: Process Sandboxing, task, P1)

Description

[Bob Owen (:bobowen) (PTO until 5th Oct)]

[Tracking Requested - why for this release]:
The plan for USER_RESTRICTED was for a staged roll-out in Fx133 and on by default in Fx134.
However, we were still seeing some big enough problems to delay the roll-out which was held at 10%.
These problems should be fixed and uplifted in Fx134.

So, now we want to do another staged roll-out in Fx134, with it on by default in Fx135.
To achieve this we need to set it to off by default in Fx134 in Beta.

Comment 1

[Bob Owen (:bobowen) (PTO until 5th Oct)]

Attachment: Bug 1936532: Disable USER_RESTRICTED by default for content process in Release for Fx134. r=gcp!

This will allow us to have a staged roll-out in Fx134.

Comment 2

[Phabricator Automation]

beta Uplift Approval Request

• User impact if declined: We will not be able to perform a staged roll-out for USER_RESTRICTED in Fx134
• Code covered by automated testing: no
• Fix verified in Nightly: no
• Needs manual QE test: no
• Steps to reproduce for manual QE testing: N/A
• Risk associated with taking this patch: Low
• Explanation of risk level: Just a pref change that puts the content sandbox on Fx134 into the same state as Fx133. This will allow us to stage the roll-out of USER_RESTRCITED in Fx134. Note this is only landing on Beta because we still want it on by default in Fx135 in Nightly.
• String changes made/needed: none
• Is Android affected?: no

Comment 3

[Pulsebot]

https://hg.mozilla.org/releases/mozilla-beta/rev/28e6f8bd2bc8

Comment 4

[Bob Owen (:bobowen) (PTO until 5th Oct)]

Didn't get closed because it landed on Beta not Nightly I think.