Closed
Bug 1851486
Opened 1 year ago
Closed 1 year ago
Deal with having / not having layers before-hand in the tab switcher.
Categories
(Firefox :: Tabbed Browser, task)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
FIXED
119 Branch
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
No description provided.
|
Assignee | |
Comment 1•1 year ago
|
||
This fixes tests that block me from landing bug 1847584. In particular,
consider that we set a tab to display: none (e.g. by entering
customize mode). Only then, we try to switch tabs.
There can be the case that painting is fast enough in clearing our
layers, and by the time we set renderLayers = false, we already do not
have layers (from display: none clearing them).
This makes transitioning to UNLOADING/LOADING potentially transition
directly to LOADED/UNLOADED, but that seems fine. That's already the
case for non-remote browsers.
This makes the remote and non-remote code-paths more similar, which is
nice.
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/02b2cc2abd3c
Deal with having/not having layers already in the tab switcher. r=dao
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox119:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•