Skip to content
This repository has been archived by the owner on Mar 5, 2019. It is now read-only.

Have tab stacks disappeared with FF 52.0? #142

Open
Jellby opened this issue Mar 8, 2017 · 7 comments
Open

Have tab stacks disappeared with FF 52.0? #142

Jellby opened this issue Mar 8, 2017 · 7 comments

Comments

@Jellby
Copy link

Jellby commented Mar 8, 2017

I've just updated to FF 52.0, and a tab stack I had is now expanded, with no indication there was ever a stack... and I can't find a way to put it back.

@yfdyh000
Copy link
Owner

yfdyh000 commented Mar 8, 2017

I can't reproduce the problem in Fx52.0 with TUF 1.5.2017.02.04.

@Jellby
Copy link
Author

Jellby commented Mar 9, 2017

Same TUF version. I've updated to FF 52.0 in another computer, and the same happened: tab stacks were "undone". Fortunately I've found out that re-stacking works fine, I just have to drag the tab vertically before stacking, otherwise I just move the tab around.

So, if you are updating to FF 52.0, take not of your tab stacks, if any, so you can re-create them. I guess this issue is just a small annoyance.

@aaronc8
Copy link

aaronc8 commented Mar 14, 2017

Same issue as well - can stack the tabs after starting the browser but it does not retain the stacking if I restart the browser.

@Doug7070
Copy link

I also have this issue. Stacking works without issue, but stacks are undone upon restarting the browser.

@Haven667
Copy link

It seems, that the problem is with migrating a session with stacked tabs from FF v51 to v52. I had the same problem. And restacking doesn't worked. After a restart the tabs were unstacked again, like mentioned. It worked for me, when I closed these stacked tabs and openend these tabs (adresses/ URLs) as new tabs. Then, after stacking again, these tabs retain after a restart. So stacking new tabs in FF v52 works without problems. At least for me.

@aaronc8
Copy link

aaronc8 commented Mar 19, 2017

@AtTheGates Wow nice, I can confirm that also did the trick for me too. Thanks for that feedback.

Interesting, maybe the devs can implement a fix more easily then

@Doug7070
Copy link

@AtTheGates Can confirm this solved the issue for me, thanks for the heads up!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants