Closed Bug 1254669 Opened 4 years ago Closed 4 years ago

Tab progress listener doesn't know that browser starts at blank after remoteness flip

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 48
Tracking Status
firefox48 --- fixed

People

(Reporter: mconley, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

We have these mTabProgressListener's attached to each tab that gets created. There's an mBlank property in each listener that causes the listener to ignore and not dispatch nsIWebProgressListener events until _after_ the initial about:blank of a browser has finished being browsed away from.

Anytime we flip remoteness, we re-use the same listener, and we don't restore the mBlank property to its initial state. That means after the remoteness flip, we pass progress events through from the about:blank load.

This causes us, among other things, to update the tab title and spinner state uselessly, which results in us painting, which causes the parent to be busy when it probably shouldn't be. This is, I believe, hurting us on our tpaint scores.

This is a relatively easy fix. I'll see if I can get a sense of how much of a tpaint win (if any) we can expect here. (It might only bear fruit with other work, like combining sync messages in the child).
Comment on attachment 8728069 [details]
MozReview Request: Bug 1254669 - Create a new mTabProgressListener for a browser when flipping remoteness. r?felipe

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/38773/diff/1-2/
Comment on attachment 8728069 [details]
MozReview Request: Bug 1254669 - Create a new mTabProgressListener for a browser when flipping remoteness. r?felipe

https://reviewboard.mozilla.org/r/38773/#review35543
Attachment #8728069 - Flags: review?(felipc) → review+
Attachment #8730828 - Attachment is obsolete: true
https://hg.mozilla.org/mozilla-central/rev/b62e261d5ff8
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 48
You need to log in before you can comment on or make changes to this bug.