Closed Bug 1578742 Opened 5 years ago Closed 5 years ago

Ship Mozilla Content Process Isolation to Beta/Release

Categories

(Core :: DOM: Content Processes, enhancement)

enhancement
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla75
Tracking Status
firefox-esr68 --- unaffected
firefox73 --- disabled
firefox74 --- wontfix
firefox75 --- verified

People

(Reporter: tjr, Assigned: tjr)

References

(Depends on 1 open bug)

Details

(Keywords: sec-want, Whiteboard: [post-critsmash-triage][adv-main75-])

Attachments

(1 file)

Bug 1557074 will enable it for Nightly; but we should wait until DocumentChannel ships until we can ship it further.

Group: core-security → dom-core-security
Keywords: sec-want
Depends on: 1582132
Assignee: nobody → tom
Group: dom-core-security → core-security-release
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla75

It means I should be waiting for Beta75 (which arrives somewhere around March 10th) to be able to test what's been tested for https://bugzilla.mozilla.org/show_bug.cgi?id=1557074 ?

Please note that the Nightly testing "[PI-147 AMO/FXA Process Isolation] QA nightly FX71 testing report" was sent on 18th of October 2019.

Flags: needinfo?(tom)

(In reply to Ioana Rusiczki from comment #3)

It means I should be waiting for Beta75 (which arrives somewhere around March 10th) to be able to test what's been tested for https://bugzilla.mozilla.org/show_bug.cgi?id=1557074 ?

Please note that the Nightly testing "[PI-147 AMO/FXA Process Isolation] QA nightly FX71 testing report" was sent on 18th of October 2019.

Yes, that is correct, this should be tested in Beta75.

Flags: needinfo?(tom)
Flags: qe-verify+
Whiteboard: [post-critsmash-triage]

As an update: Testing on Beta75 is in progress.

I did not find problems which seem to be generated by this issue.
The issues I filed are related to server delays and UI.
https://github.com/mozilla/bedrock/issues/8664
https://github.com/mozilla/fxa/issues/4545

The test cases https://testrail.stage.mozaws.net/index.php?/reports/view/2598 related to PI-147 https://jira.mozilla.com/browse/PI-147 were tested on on FF75beta on Win10 where the pref "browser.tabs.remote.separatePrivilegedMozillaWebContentProcess" is automatically set on true.

I tested the addon installs on addons.mozilla.org : install, remove, enable states work as expected.
I checked on fxA: connect, disconnect, reconnect the account, tabs and sync operations when the user is connected on two devices, creation of an account, the sign in and sign out from SUMO, the basic account setting operations, deleting an fxA account and it seems to be all working as expected.

I'm going to mark this issue verified.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main75-]
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: