Closed Bug 1603196 Opened 5 years ago Closed 5 years ago

process switching fires spurious nsIWebProgressListener events to RemoteWebProgress

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla74
Fission Milestone M5
Tracking Status
firefox74 --- fixed

People

(Reporter: mattwoodrow, Assigned: mattwoodrow)

References

Details

Attachments

(1 file)

When we process switch we stop and destroy the old docshell, and create a new docshell in the new process.

Stopping the old docshell fires a STATE_STOP notification, and resuming the load in the new docshell fires a STATE_START notification. We also fire a START/STOP pair for the initial about:blank load in the new docshell.

These notifications probably make sense in the scope of their local process, but from the perspective of RemoteWebProgress in the parent, we probably want to suppress them, since it's all one logical load.

This doesn't block the STATE_START notification from the new process, as we currently have a second start notification (when DocumentChannel redirects to the real channel), so this is unchanged.

Assignee: nobody → matt.woodrow
Fission Milestone: --- → M5
Priority: -- → P2

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:mattwoodrow, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(matt.woodrow)
Pushed by mwoodrow@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bf551ae8dece
Skip START_STOP notifications from old process being delivered to RemoteWebProgress when process switching during a load. r=kmag,nika
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
Flags: needinfo?(matt.woodrow)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: