Sometimes when I browse news threads, or read my email threaded, some threads 'forget' about their children... meaning that even though the container/twisty is collapsed, there are children displayed (and the thread-lines are drawn). It seems as if the container/twisty state gets messed up somehow. I encounter this quite often nowadays - and I don't know what causes it, but it's really annoying.
CC hyatt in case he has seen this, or know the problem.
Created attachment 67240 [details] Step 1 Step 1: see the broken thread in the middle of the screenshot.
Created attachment 67241 [details] Step 2 Step 2: this is how it looks like when I click the twisty. If I click it again, one duplicate will disappear, and we go back to a state where it looks like in "Step 1".
Assignee: hewitt → varga
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.0
I can reproduce this now all the time. For a mailing list I participate in, when I click on a thread with *only* new messages, the thread twisty collapses when I read the first message in the thread - the message that started thread. Sorry for such a fuzzy explanation, but this is the best I can do. :-)
Still happening very often in RC1. When I select the "main" message of an expanded thread (i.e. the one with the twisty beside it), the twisty will often collapse -- but the thread is still expanded -- and the twisty shouldn't have been collapsed in the first place. Hope this clarifies this bug a bit.
Summary: Sometimes outliner threads 'forget' about a child → Twisty collapses (erroneously) while the thread is still expanded
More info: it happens often when browsing newsgroup threads in mailnews. It happens both on Linux and Windows.
Nav triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
hwaara, look at bug 123858
Sounds like a dup. *** This bug has been marked as a duplicate of 123858 ***
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.