Closed Bug 1542790 Opened 6 years ago Closed 6 years ago

Use GetParent or GetTop for nsGlobalWindowInner

Categories

(Core :: DOM: Content Processes, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Fission Milestone M2
Tracking Status
firefox68 --- fixed

People

(Reporter: nika, Assigned: nika)

References

Details

Attachments

(5 files)

No description provided.

This is required to support getting the parent and top properties from
within remote subframes.

No longer blocks: fission
Status: NEW → ASSIGNED

This prevents cross-process window proxies for being created for remote
browsers embedded in a content browser, as well as establishing a boundary at
<iframe mozbrowser>

Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5fde2cc9277a Part 1: BC::GetParent on toplevel windows should be self, r=peterv https://hg.mozilla.org/integration/autoland/rev/607e1bc95c9b Part 2: Use BC::GetParent and BC::GetTop for local windows, r=peterv https://hg.mozilla.org/integration/autoland/rev/4a3f5fbd5011 Part 3: Make nsIDOMMozBrowserFrame builtinclass, r=bzbarsky https://hg.mozilla.org/integration/autoland/rev/f29d6ec6c75a Part 4: Change definition of toplevel content to match reality in nsFrameLoader, r=qdot https://hg.mozilla.org/integration/autoland/rev/31afeed0ac1d Part 5: Relax toplevel BC requirements, r=qdot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: