644055 - Grouped tabs are rearranged after exiting and re-opening firefox 4

Status: RESOLVED DUPLICATE of bug 628188

(Firefox Graveyard :: Panorama, defect)

Description

[David Bishop]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0

The grouped tab function re-arranges tabs within groups when exiting firefox and re-opening.

For example if I have websites A, B, C, D in Tab Group 1 and sites E, F, G, H in Tab Group 2 and I, J, K in group 3 when I exit firefox when I open it later sites A, D, F, I will be in group 1 while C, E, K will be in group 2 and B, G, H J in group 3. 

Reproducible: Always

Steps to Reproduce:
1.Open Grouped tabs
2.Put multiple tabs in more than 1 group
3.Exit firefox
4.Re-open firefox and go to grouped tabs
Actual Results:  
Tabs were not in the groups that I had them in when I closed the program.

Expected Results:  
Tabs should stay in the groups I place them in when I re-open the program.

Comment 1

[Tim Taubert [:ttaubert] (inactive)]

Looks like another dupe of bug 628188. Does the problem still exist after disabling all add-ons and restarting _twice_?

Comment 3

[gossi]

I can confirm this bug. Happens even with more than two tab groups. It's like playing memory after each startup... :(

I'm on OSX Snow as well with Firefox 4.0

Comment 4

[Tim Taubert [:ttaubert] (inactive)]

Do you have any add-ons installed? Can you please disable all of them and restart Firefox _twice_? The problem should be gone after that.

Comment 5

[gossi]

Hey Tim,

I thanks for your tip. Did not worked quite well though. What I did:

1. Deactivated all extensions and plugins, hit restart
2. Quit firefox, start again
3. Quit firefox, start again
4. Go to TabGroups, resorted my tabs
5. Quit firefox, start again
6. Checked my tabgroups, everything fine.
7. Activated extensions and plugins, quit firefox, start again
8. Tabs are unsorted again.

Comment 6

[Tim Taubert [:ttaubert] (inactive)]

Thanks for checking, so that bug is a duplicate as I expected. Unfortunately that requires the add-on owner to update their add-ons using the newest Addon-SDK, that's the source of the error.