(In reply to Rob Wu [:robwu] from comment #4) > This bug was originally filed because bug 1819675 was going to change the behavior of `sessions.restore`. > After some rounds of review feedback and patch revisions (in https://phabricator.services.mozilla.com/D174501 ), the final version ended up preserving the original behavior of `sessions.restore` . > > Because of that, I am inclined to close this bug. > > As a precaution, I'm moving this to the Dev Outreach component, so that we can reach out to the top add-ons that use the `sessions` API, to see if there are any regressions from the expanded list of entries in `sessions.getRecentlyClosed`. Now that persisting closed tabs between sessions has landed in Nightly (behind a pref), we should definitely have developers test this to see if that poses a problem as mentioned in [comment 3](https://bugzilla.mozilla.org/show_bug.cgi?id=1836877#c3).
Bug 1836877 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Rob Wu [:robwu] from comment #4) > This bug was originally filed because bug 1819675 was going to change the behavior of `sessions.restore`. > After some rounds of review feedback and patch revisions (in https://phabricator.services.mozilla.com/D174501 ), the final version ended up preserving the original behavior of `sessions.restore` . > > Because of that, I am inclined to close this bug. > > As a precaution, I'm moving this to the Dev Outreach component, so that we can reach out to the top add-ons that use the `sessions` API, to see if there are any regressions from the expanded list of entries in `sessions.getRecentlyClosed`. Now that persisting closed tabs between sessions has landed in Nightly (behind a pref), we should definitely have developers test this to see if that poses a problem as mentioned in [comment 3](https://bugzilla.mozilla.org/show_bug.cgi?id=1836877#c3). :luca, are you responsible for outreach?