1600055 - Get rid of using "outerWindowID" in favor of "browsingContext.id"

Status: RESOLVED FIXED

(Remote Protocol :: Agent, task, P1)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Currently we still use the outerWindowId to reference frames. As we know for each process switch the id will change, and as such invalidates references for clients. To be Fission compatible we will have to purely make use of browsingContext.id.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

It would be good to actually already get this done before starting the work on JSWindowActor (bug 1565162).

Comment 2

[Andreas Tolfsen ❲:ato❳]

Cases where outerWindowID is used:
https://searchfox.org/mozilla-central/search?q=outerWindowID&path=remote%2F

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

To pave the way for Fission I'm going to take this up now.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=c671eac9b801a46508d39e7e46c68d80071a6dd9

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: Bug 1600055 - [remote] Switch from using "outerWindowID" to "browsingContext.id".

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0320f52f97bb
[remote] Switch from using "outerWindowID" to "browsingContext.id". r=remote-protocol-reviewers,ato

Comment 7

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/0320f52f97bb