562540 - Migration assistant shouldn't display a useless page and should resolve add-on conflicts

Status: RESOLVED INVALID

(Thunderbird :: General, defect)

Description

[Eric Moore]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.5pre) Gecko/20100427 Thunderbird/3.1b2

I installed build 1 of Thunderbird 3.1 beta 2. One page in the migration assistant tells me that it noticed that I had been using the Compact Message Reader View add-on and recommends I use the CompactHeader Toolbar instead, and then mentions its already installed. Another page tells me that it noticed that I has been using "advanced folder columns", recommends that I use the "extra columns" add-on and then mentions that its already installed

1. If there is nothing for me to do in a page, don't display it. 

2. Detecting that I had been using an uninstalled extension is unsettling. Why is there any record for Thunderbird to notice? If its detecting settings that hadn't been removed when the add-on was uninstalled I suggest it check something like extensions.rdf instead. 

3. It claims I have ExtraColumns and CompactHeader Toolbar installed. I don't, according to tools-> add-ons.

https://addons.mozilla.org/en-US/thunderbird/addon/45601 mentions that the functionality of the CustomizeHeader Toolbar is also in the CompactHeader add-on, and that if you're using 3.1 beta 2 or newer you don't need the CustomizeHeader Toolbar add-on anymore. This makes me suspect that the migration assistant is detecting an add-on that is built into 3.1 beta 2 and treating it as if it were a user installed add-on. That is confusing. 

In tools -> add-ons the CustomizeHeader Toolbar add-on has a red triangle next to it and "not compatible with Thunderbird 3.1b2" displayed in red, though it does work. Is this due to the features of the CompactHeader add-on being built into 3.1 beta 2 and the two add-ons conflicting? If so, the migration assistant should tell me to disable the the CustomizeHeader Toolbar add-on.


Reproducible: Always

Comment 1

[Mark Banner (:standard8)]

When I marked this as blocking beta 2, I incorrectly assumed it was about the extensions not being compatible, however now I read it again, that's clearly not the case, so clearing blocking and assigning to Blake to have a look at.

Comment 2

[Blake Winton (:bwinton) (:☕️)]

I'm clearly not going to have time to look at this anytime soon, so I'm freeing it up for someone in the community to take.

Comment 3

[Wayne Mery (:wsmwk)]

MA was removed in TB14-15, so no longer an issue