Closed Bug 366758 Opened 18 years ago Closed 18 years ago

Additional Folders View Extension changes order position of multiple inboxes

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: clayberkley, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20070111 Thunderbird/2.0b1 - Build ID: 2007011103 On initial launch, default IMAP account is shown on top. If I toggle to other views and back to the Favorites view, the default account is dropped below my secondary and I can only get it back on top by restarting TB. Reproducible: Sometimes Steps to Reproduce: 1) Launch TB (default account is in its position at the top) 2) Toggle through views and back to Favorites view in order to display missing favorite folders. 3) Default folder is now dropped below secondary and will not return to top until TB is restarted. Actual Results: On one computer, this is the consistent behavior. On another, it is difficult to reproduce. Expected Results: Default IMAP account's Inbox should remain in the topmost position regardless of toggling the views.
You mention "extension" in the summary -- if your problem only occurs with the extension, it's not a Thunderbird bug; you need to file the bug with the extension author.
I was asked by the extension author to file this bug with Bugzilla, specifically stating, "I see what you mean. Yes, could you please report this in Bugzilla since it's a TB problem, and send me the bug number so I can track it." I would say it's more of a problem with the extension. Therefore, I will close the bug as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
There may in fact be a bug in TB, but the author needs to prove that; it's not something that can be determined by the users of the extension.
The extension is not needed to see this bug. See Bug 367049 instead.
You need to log in before you can comment on or make changes to this bug.