1622420 - Can't get top-level WindowContext in the cross-origin iframe

Status: RESOLVED FIXED

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

Description

[Dimi Lee [ooo Mar. 28 - Apr. 6]]

Steps to reproduce:

1. Apply the attached patch which prints log when users interact with a document
2. Go to https://dimidl.github.io/test/iframe/cross-origin-iframe.html
3. mouse click the iframe
4. debug message indicates there is no top-level window context

Notes.
top-level window context can be found in a same-origin iframe.
https://dimidl.github.io/test/iframe/same-origin-iframe.html

Comment 1

[Dimi Lee [ooo Mar. 28 - Apr. 6]]

Attachment: 0001-Fission-Window-Context-test.patch

Comment 2

[Chris Peterson [:cpeterson]]

Tracking for Fission M5b or early M6a to determine what's happening

Are we not sync'ing WindowContexts properly? Nika says this is unlikely to be a race because this code runs late after navigation has settled.

Peter will ping afarre tomorrow.

Comment 3

[Peter Van der Beken [:peterv]]

Attachment: Bug 1622420 - Set the current WindowContext for BrowsingContexts newly created over IPC. r?farre!

Comment 4

[Peter Van der Beken [:peterv]]

Attachment: Bug 1622420 - Cleanup docshell/test/browser/browser_bug422543.js. r?farre!

Depends on D68572

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0e43ffd5251c
Set the current WindowContext for BrowsingContexts newly created over IPC. r=farre
https://hg.mozilla.org/integration/autoland/rev/1ad327ce20e3
Cleanup docshell/test/browser/browser_bug422543.js. r=farre

Comment 6

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/0e43ffd5251c
https://hg.mozilla.org/mozilla-central/rev/1ad327ce20e3