Open Bug 1355456 Opened 2 years ago Updated 6 months ago

Investigate preparing the next tab on mousedown on the tab close button


(Firefox :: Tabbed Browser, enhancement, P3)





(Reporter: florian, Unassigned)


(Blocks 2 open bugs)


(Keywords: perf, Whiteboard: [qf:p5:responsiveness][fxperf:p3])

We should see if there are things that can be done to improve the perception of speed when the user is about to close a tab.
- can we prepare the tab that will be displayed next by removing any throttling of JS there?
- if the next tab is a lazy browser after a session restore, should we start loading the page in it?
- can we reduce the priority of the current tab's JS so that we have more resources available for the next tab that will be shown?
- how badly would we break the web if we fired the onbeforeunload even on mousedown on the close button rather than on click?
Whiteboard: [photon][qf] → [qf]
Flags: qe-verify?
Priority: -- → P2
Whiteboard: [qf] → [photon-performance] [qf]
Whiteboard: [photon-performance] [qf] → [photon-performance] [qf:investigate]
Priority: P2 → P3
Whiteboard: [photon-performance] [qf:investigate] → [reserve-photon-performance] [qf:investigate]
Flags: qe-verify? → qe-verify+
QA Contact: adrian.florinescu
Keywords: perf
Whiteboard: [reserve-photon-performance] [qf:investigate] → [reserve-photon-performance] [qf:investigate] [fxperf]
Bug 1430292 applied some of this idea with tab warming, but comment 0 has more ideas that might be worth pursuing, so let's keep this bug around.
Whiteboard: [reserve-photon-performance] [qf:investigate] [fxperf] → [qf:investigate] [fxperf:p3]
Flags: needinfo?(mconley)
Flags: needinfo?(mconley)
Whiteboard: [qf:investigate] [fxperf:p3] → [qf:responsiveness:p5][fxperf:p3]
Whiteboard: [qf:responsiveness:p5][fxperf:p3] → [qf:p5:responsiveness][fxperf:p3]
You need to log in before you can comment on or make changes to this bug.