607621 - Downgrade/upgrade FF4->FF3.6->FF4 loses tabs

Status: RESOLVED WONTFIX

(Firefox Graveyard :: Panorama, defect)

Description

[Benjamin Smedberg]

I've had this happen twice now on Mac.

STR:
* don't use tabcandy
* In FF4, Open a Window with two app tabs and a bunch of regular tabs
* Close, open FF 3.6 (in my case, accidentally)
* Close FF3.6, Open FF4 again
* Initially, all the tabs show up, no app tabs. This is ok with me.
* I choose to make the first two tabs app-tabs again.
* When I make the second tab an app-tab, all the other tabs disappear.

Opening tabcandy at this point shows me a bunch of tiny tabs in the corner of my screen which are not grouped into any windows. It feels like we need some sort of validation of the tabcandy data on upgrade so that it doesn't hide windows.

Comment 1

[Dietrich Ayala (:dietrich)]

Executed all steps with a new profile, WFM on Linux.

Comment 2

[Kevin Hanes]

(In reply to comment #0)
If the STR are followed, and you never use Tab Candy, then I am not sure that Tab Candy could be causing the described behavior.

Two things to consider:
* Are you on the latest nightly, and is this still happening?
* Is it possible that you activated Tab Candy somehow?

I suspect this is filed for the wrong component.

Comment 3

[Benjamin Smedberg]

Yes, I'm running nightlies. It happens pretty consistently when I do this. I certainly may have accidentally opened tabcandy at some point, but I've never set up different tab groups or anything like that. I called it a tabcandy bug because that's the only code I know of which causes tabs to disappear but still be present in the tabcandy view when I do open it.

I'm happy to attach a set of sessionstore files if that would help, I think... need to check whether there is any private data.

Comment 4

[Ian Gilman [:iangilman]]

Benjamin, can you repro on today's nightly with a fresh profile? At the very least, you shouldn't get the "tiny tabs in the corner" now that bug 598600 has landed.

Comment 5

[Kevin Hanes]

This seems like an edge-case that we won't get to until post ff4.0, at which point, there's almost no point to fixing it. This is especially true if the landing of bug 598600 mitigates this bug.

Comment 6

[Johnathan Nightingale [:johnath]]

I can understand this hurting dogfooding, but I don't think it blocks the release since it doesn't describe a common user scenario.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

Isn't WORKSFORME more accurate? I don't really see what part of this wasn't addressed by bug 598600.