Closed Bug 1586050 Opened 4 years ago Closed 4 years ago

Don't blow away progress listeners when switching between local and remote processes

Categories

(Core :: DOM: Navigation, task, P2)

Product:
Core
Component:
DOM: Navigation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla71
Project Flags:
Fission Milestone M4
Tracking Flags:
Tracking Status
firefox71 --- fixed

People

(Reporter: u608768, Assigned: u608768)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 1586050 - Don't blow away progress listeners when switching between local and remote processes, r=kmag
47 bytes, text/x-phabricator-request
Details | Review

We currently lose RemoteWebProgress event listeners when switching between local and remote processes.

This came up while working on bug 1578465 and bug 1585777.

Fission Milestone: --- → M4

Whenever we do a process switch, the <browser> gets a new WebProgress instance.
When that happens, we currently handle transferring listeners from one
RemoteWebProgress instance to another, but not from a local to remote, or vice
versa. This patch changes that by tracking listeners added to the <browser> and
manually re-adding them after a process switch occurs.

Pushed by kmadan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3d1345e406d5
Don't blow away progress listeners when switching between local and remote processes, r=kmag

https://hg.mozilla.org/mozilla-central/rev/3d1345e406d5

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox71: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Regressions: 1588177
You need to log in before you can comment on or make changes to this bug.