Closed
Bug 1289395
Opened 8 years ago
Closed 6 years ago
incorrect tab switching behaviour (order) after reopening a closed tab with CtrlTab previews
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1292049
People
(Reporter: yakov-litvin-public, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.83 Safari/537.36 Vivaldi/1.3.544.25
Steps to reproduce:
1. open at least 3 tabs (let's call them A, B, C); I always have many open tabs, so I'm not 100% sure this will work the same way for only 3
2. close tab C
3. reopen it using ctrl+shift+T or other way
4. ctrl+tab back to B
5. alt+tab again
Actual results:
we are switched to the A tab;
if we hold alt in step 4, we can see that C is neither the first nor the second in the alt+tab previews. For multiple open tabs (my case) C is not listed there at all; not sure what will happen if there's just 3 tabs. For multiple tabs, there's no way to get to C via alt+tab at all (except through going to the whole list of tabs)
Expected results:
we are switched to the C tab;
if we hold alt in step 4, we can see C as the first item in the alt+tab previews (we're switching from it, right?)
Reporter | ||
Updated•8 years ago
|
Component: Untriaged → Tabbed Browser
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Comment 1•8 years ago
|
||
I can reproduce this but I needed to set browser.ctrlTab.previews=true.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Summary: incorrect tab switching behaviour (order) after reopening a closed tab → incorrect tab switching behaviour (order) after reopening a closed tab with CtrlTab previews
Updated•6 years ago
|
Flags: needinfo?(dao+bmo)
Updated•6 years ago
|
Comment 2•6 years ago
|
||
I can't seem to reproduce this (anymore). Jared, can you?
Flags: needinfo?(jaws)
Updated•6 years ago
|
No longer blocks: ctrl-tab-panel
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jaws)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•