Closed
Bug 1257453
Opened 8 years ago
Closed 8 years ago
Restoring into existing tab with mismatch userContextId should create a new tab
Categories
(Firefox :: Session Restore, defect, P2)
Firefox
Session Restore
Tracking
()
RESOLVED
DUPLICATE
of bug 1274461
People
(Reporter: allstars.chh, Assigned: allstars.chh)
References
(Blocks 1 open bug)
Details
(Whiteboard: [userContextId])
See ttaubert's and sicking's comments in https://bugzilla.mozilla.org/show_bug.cgi?id=1250063#c38 https://bugzilla.mozilla.org/show_bug.cgi?id=1250063#c42
Updated•8 years ago
|
Whiteboard: [userContextId]
Updated•8 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•8 years ago
|
||
Hi Tanvi Do you have more reasons to make this P1? From https://bugzilla.mozilla.org/show_bug.cgi?id=1245502#c9 I thought session restore is not in priority, also that bug is P2. And this bug is 'restore into an *existing* tab', which makes the use case is less than regular restore. From Jonas' comment from Comment 0, I think he doesn't know we restore into existing tabs, which I think the use case for this bug is pretty rare.
Flags: needinfo?(tanvi)
Comment 2•8 years ago
|
||
Spoke to Yoshi about why this is a P1. We want to ensure that we don't change ever change the usercontextId on an existing tab.
Flags: needinfo?(tanvi)
Assignee | ||
Comment 4•8 years ago
|
||
When working on Bug 1274461 I found that it will have the case that existing tab has different userContextId, for example, in about:home, there's a 'restore last session' button. If we have container tab in the previous session, then when 'Restore Last Session' is pressed, the about:home tab will be used to restore the first container tab. So I'll duplicate this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•