Recently-closed tabs lists should include closed tabs from recently closed windows
Categories
(Firefox :: Session Restore, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: sfoster, Assigned: sfoster)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-firefox-view] )
Attachments
(2 files)
When we are building the list of recently closed tabs for firefox view and the history menus, it should include the closed tab lists from recently closed windows. These are not the tabs which were open at the time the window was closed - which is bug 1831229
Updated•3 years ago
|
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
:robwu, I'd like to preemptively de-couple this bug from any discussion of extension API changes by again avoiding any change to what the session API does and returns in the patch I'm developing for this bug. When that lands, it will introduce a gap between the behavior in the browser UI - in terms of what the recently-closed tabs menus show vs what sessions.getRecentlyClosed returns. If we break that out into its own bug we can discuss if or when we want to close that gap to enable extension developers to also retrieve and restore closed tabs from closed windows. Does that sounds like a reasonable plan? We'll still need to watch out for unintentional regressions from the patch I land here of course.
Comment 2•3 years ago
|
||
(In reply to Sam Foster [:sfoster] (he/him) from comment #1)
:robwu, I'd like to preemptively de-couple this bug from any discussion of extension API changes by again avoiding any change to what the
sessionAPI does and returns in the patch I'm developing for this bug. When that lands, it will introduce a gap between the behavior in the browser UI - in terms of what the recently-closed tabs menus show vs whatsessions.getRecentlyClosedreturns. If we break that out into its own bug we can discuss if or when we want to close that gap to enable extension developers to also retrieve and restore closed tabs from closed windows. Does that sounds like a reasonable plan? We'll still need to watch out for unintentional regressions from the patch I land here of course.
That sounds like a very reasonable path forwards. The API does not need to change; extensions can already query all recently closed tabs (including inside closed windows) through the API. If there is ever a desire to change the API, make sure to update bug 1836877 (for dev outreach).
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 3•2 years ago
|
||
Depends on D185108
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
- Move closeTab and openAndCloseTab to the helpers module and replace a couple of uses
- Move waitForBrowserState/promiseBrowserState and replace a couple of uses
Comment 6•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/fb1598dc258f
https://hg.mozilla.org/mozilla-central/rev/feb42cf3b6e1
| Assignee | ||
Updated•2 years ago
|
Description
•