Open
Bug 1303911
Opened 8 years ago
Updated 2 years ago
restoring a single container tab quickly opens a second tab that disappears instantly
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox52 | --- | wontfix |
| firefox53 | --- | affected |
| firefox54 | --- | affected |
| firefox55 | --- | unaffected |
| firefox57 | --- | fix-optional |
People
(Reporter: kjozwiak, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [userContextId][domsecurity-backlog])
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
issue.png
When restoring a single container tab while using "Show my windows and tabs from last time" under about:preferences#general, you'll notice that a second tab quickly opens and closes before the original container tab is completely restored. This seems to only happen when you have a single container tab opened and doesn't occur when you have multiple containers. I couldn't reproduce this behaviour with a default container either, so it seems this is container specific.
Example: https://youtu.be/kuWqWRIcF6E
STR:
* install the latest version of m-c
* select "Show my windows and tabs from last time" under about:preferences#general
* open a personal container via file -> new container tab
* once opened, load gmail.com and close fx
* re-open fx and you'll notice that for a split second, fx loads two tabs and quickly closes one
|
||
Comment 1•8 years ago
|
||
It looks like session restore is creating a non-default Container tab and putting it first for a split second.
Why?
|
Reporter | |
Comment 2•8 years ago
|
||
I've attached a screenshot from the video in comment#0 so it's easier to see the problem.
|
|
||
Updated•8 years ago
|
Priority: -- → P2
|
||
Comment 3•8 years ago
|
||
Mass wontfix for bugs affecting firefox 52.
|
|
Reporter | |
Comment 4•7 years ago
|
||
I couldn't reproduce this anymore with fx55.0a1 after several attempts. However, it's still reproducible with fx54.0b12 and fx53.0.3.
Using macOS 10.12.5x64:
* fx55.0a1, buildid: 20170530030204, changeset: 286f71223256 - couldn't reproduce the issue
* fx54.0b12, buildid: 20170529025116, changeset: 715d88d0bd82 - reproduced the issue
* fx53.0.3, buildid: 20170518000419, changeset: 1fe643b3421a - reproduced the issue
status-firefox53:
--- → affected
status-firefox54:
--- → affected
status-firefox55:
--- → unaffected
|
||
Comment 5•7 years ago
|
||
Kamil: does comment 4 mean we should close this WORKSFORME?
Flags: needinfo?(kjozwiak)
|
||
Comment 6•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
|
||
Comment 7•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
|
||
Comment 8•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Flags: needinfo?(kamiljoz)
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•