Closed Bug 534883 Opened 15 years ago Closed 15 years ago

Threads Expanded Randomly

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 232562

People

(Reporter: david, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 My Thunderbird setup: View > Layout > Wide View View > Threads > Threads with Unread View > Sort by > {Order Received, Ascending, Threaded} Ad-ons: TB3 Classic theme 1.1.5 Signature Switch 1.6.4 Compact Headers 1.1.4 I'm seeing a problem similar to what was reported in bug #232562. In accord with the last comment there, I'm filing a new bug report. When I open a newsgroup, one thread is generally expanded even though I previously collapsed all threads (including the one that is now expanded). Unlike bug #232562, (1) it doesn't always happen and (2) it's not always the first thread. The expanded thread always has a new message. Reproducible: Sometimes Yes, I've also seen this while using Thunderbird in the safe mode.
David if you disable the extensions is the issue still present ?
"Yes, I've also seen this while using Thunderbird in the safe mode." [last line of Description] Safe mode disables all extensions and themes. I've pretty much viewed all the newsgroups in my accounts. I'll have to wait a few hours for them to repopulate with new messages before I can test this again.
I again saw this problem while using Thunderbird 3 in safe mode. While Thunderbird was still open, I went to [Tools > Ad-ons] in the menu bar. The Ad-ons Manager reported that all ad-ons were disabled.
Ho I forgot to ask, if there was any messages in the Tools -> Error console ?
With the All button selected on the Error Console window selected, the window was blank.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.