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

NEW
Unassigned

Status

()

Firefox
Tabbed Browser
P3
normal
8 months ago
7 days ago

People

(Reporter: florian, Unassigned)

Tracking

(Blocks: 2 bugs, {perf})

unspecified
Points:
---
Dependency tree / graph
Bug Flags:
qe-verify +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [reserve-photon-performance] [qf:investigate])

(Reporter)

Description

8 months ago
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.
Eg.
- 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?

Updated

7 months ago
Whiteboard: [photon][qf] → [qf]

Updated

7 months ago
Flags: qe-verify?
Priority: -- → P2
Whiteboard: [qf] → [photon-performance] [qf]
Whiteboard: [photon-performance] [qf] → [photon-performance] [qf:investigate]
Blocks: 1363755
(Reporter)

Updated

7 months ago
No longer blocks: 1348289

Updated

6 months ago
Priority: P2 → P3
Whiteboard: [photon-performance] [qf:investigate] → [reserve-photon-performance] [qf:investigate]

Updated

6 months ago
Flags: qe-verify? → qe-verify+
QA Contact: adrian.florinescu
Keywords: perf
You need to log in before you can comment on or make changes to this bug.