Closed Bug 1532661 Opened 1 year ago Closed 1 year ago

Support syncing complete BrowsingContextGroups over IPC

Categories

(Core :: DOM: Core & HTML, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Fission Milestone M2
Tracking Status
firefox67 --- fixed

People

(Reporter: nika, Assigned: nika)

References

Details

Attachments

(6 files)

This is needed to support adding new content processes to participate in the browsing context group dynamically.

This patch does not cover allowing a content process to leave the BrowsingContextGroup.

Duplicate of this bug: 1529561
Component: DOM → DOM: Core & HTML
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/84d076d2163d
Part 1: Perform basic validation on CanonicalBrowsingContext, r=farre
https://hg.mozilla.org/integration/autoland/rev/a39da23d450b
Part 2: Use a field list macro header for synced fields, r=farre
https://hg.mozilla.org/integration/autoland/rev/58f77fa35eea
Part 3: Add WillSetX and DidSetX callbacks for BrowsingContext synced fields, r=farre
https://hg.mozilla.org/integration/autoland/rev/9ce1a2365aff
Part 4: Support initializing complete BrowsingContextGroups in a single op with an IPCInitializer struct, r=farre
https://hg.mozilla.org/integration/autoland/rev/856a3d16a4ca
Part 5: Make the BrowsingContext opener edge a weak reference, r=farre
https://hg.mozilla.org/integration/autoland/rev/97c2ee22169c
Part 6: Clean up BrowsingContext references more reliably, r=farre

Part 1 here broke mouse events for out-of-process iframes. Bug 1539069.

Regressions: 1535835
Blocks: 1582832
No longer blocks: 1582832
Regressions: 1582832
No longer regressions: 1582832
You need to log in before you can comment on or make changes to this bug.