empty group doesn't removed from closedGroups when closed tabs restored one at a time
Categories
(Firefox :: Session Restore, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox133 | --- | unaffected |
| firefox134 | --- | unaffected |
| firefox135 | --- | fixed |
People
(Reporter: tabmix.onemen, Assigned: jswinarton)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-tabgrps-sessionstore] )
Bug 1927774 add the ability to restore tabs form closed tab group.
After restoring all tabs from a deleted group SessionStrore does not remove the group from winData.closedGroups
The result of this 'ghost' group is that any attempt to reopen other closed tabs when there are other closed groups fails with this error
Uncaught NS_ERROR_ILLEGAL_VALUE: Invalid index: not in the closed tabs
ssi_undoCloseTab resource:///modules/sessionstore/SessionStore.sys.mjs:4079
ss_undoCloseTab resource:///modules/sessionstore/SessionStore.sys.mjs:449
undoCloseTab chrome://browser/content/browser.js:6042
oncommand chrome://browser/content/browser.xhtml:1
2 SessionStore.sys.mjs:4079
Steps to reproduce:
- open few tabs
- create group
- delete the group
- go to
History > Recently Closed Tabsand restore each tab from that group. - create another group and delete it.
Result:
- any call to
undoCloseTab()will fail with the above error
Updated•1 year ago
|
Comment 1•1 year ago
|
||
:sthompson, since you are the author of the regressor, bug 1927774, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•1 year ago
|
||
This is not really a regression -- this is a bug with new functionality that's behind a feature flag.
This is definitely an oversight from the implementation. If a tab is restored from a closed group and that causes the closed group to have no more remaining tabs, we should remove the closed group data from the session.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
I think that if bug 1927765 is resolved, this specific bug will be fixed.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
The severity field is not set for this bug.
:sclements, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Reporter | ||
Comment 6•1 year ago
|
||
YES,
it is fixed by bug 1927765
Updated•1 year ago
|
Description
•