558303 - Can't read a message from a thread - because can't expand the thread and only get the summary view with operate_on_msgs_in_collapsed_threads = true

Status: RESOLVED WORKSFORME

(Thunderbird :: Folder and Message Lists, defect)

Description

[Ludovic Hirlimann [:Usul]]

Attachment: Screenshot where I'm stuck in multimessage view

So once in a while I'm stuck in a view that looks like the screen shot. I 'm viewing a thread that only contains one unread message. pressing the right arrow or clicking on either the arrow or the read column does nothing in my case.

I'm using View -> Sort by -> {Date,Ascending,Threaded}
          View -> Threads -> Unread

Switching to Threads with unread doesn't change the issue.

I can read the message because the only thing I getting is the multimessage containing all the thread. I can fix that by using the view folder widget and selecting "unread" or by using the mail filter bar extension and selecting unread too.

I have a copy of my complete profile saved just as a testcase for this. I'll share it but not publicly.

I hope my description above is clear.

I'm filling a new bug because I'm not sure this is bug 526988 nor bug 523604.
I'm requesting blocking because this kills my ability to read bugmail :-)

Comment 1

[Phil Pishioneri]

I am also seeing this behavior, which is new in update 3.0.4. I downloaded 3.0.3 to confirm: it does not have the problem.

Comment 2

[Dan Mosedale (:dmosedale, :dmose)]

This:

> I can read the message because the only thing I getting is the multimessage
> containing all the thread. I can fix that by using the view folder widget and
> selecting "unread" or by using the mail filter bar extension and selecting
> unread too.

doesn't appear to me to be entirely consistent with this:

> I'm requesting blocking because this kills my ability to read bugmail :-)

In part because so far we only know of two people who are affected.  

Does the workaround of clicking on the name of the message sender in the multi-message view open the message?

Thanks to Standard8's handy status tracking page 

http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugtracking/index.html?branch=3.0

and Phil's work figuring out that this is new since 3.0.3, it looks like the regression window is 

http://hg.mozilla.org/releases/comm-1.9.1/pushloghtml?startdate=2010-02-27+13%3A18&enddate=2010-03-17+09%3A49

My guess would be that this is a regression from bienvenu's checkin for bug 534858, so adding him to the CC for his thoughts.





* can you find the regression range

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)
> This:
> 
> > I can read the message because the only thing I getting is the multimessage
> > containing all the thread. I can fix that by using the view folder widget and
> > selecting "unread" or by using the mail filter bar extension and selecting
> > unread too.
> 
> doesn't appear to me to be entirely consistent with this:
> 
> > I'm requesting blocking because this kills my ability to read bugmail :-)

Well I can read the subject but not the body.
 
> In part because so far we only know of two people who are affected.  
> 
> Does the workaround of clicking on the name of the message sender in the
> multi-message view open the message?

No that doesn't do anything.
 
> Thanks to Standard8's handy status tracking page 
> 
> http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugtracking/index.html?branch=3.0
> 
> and Phil's work figuring out that this is new since 3.0.3, it looks like the
> regression window is 
> 
> http://hg.mozilla.org/releases/comm-1.9.1/pushloghtml?startdate=2010-02-27+13%3A18&enddate=2010-03-17+09%3A49
> 
> My guess would be that this is a regression from bienvenu's checkin for bug
> 534858, so adding him to the CC for his thoughts.

Spot on. 
Broken in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100312 Shredder/3.0.4pre

Working in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.8) Gecko/20100310 Shredder/3.0.4pre

Comment 4

[Phil Pishioneri]

(In reply to comment #2)
> Does the workaround of clicking on the name of the message sender in the
> multi-message view open the message?

No effect for me for that message or any other message's sender in that view (single or double clicking).

I also notice that the unread message is listed twice in that multi-message view: once in its correct position, and also at the top of the list. This behavior is only while viewing unread: if I switch to "View -> Threads -> All", it's only listed once (with the entire thread selected).

Comment 5

[David :Bienvenu]

Did you read the unread child message, and then collapse the thread?

Comment 6

[Phil Pishioneri]

(In reply to comment #5)
> Did you read the unread child message, and then collapse the thread?

Me? When? I tend to leave threads expanded (or expand all with "*" upon entering a folder with some collapsed threads).

Comment 7

[Ludovic Hirlimann [:Usul]]

(In reply to comment #5)
> Did you read the unread child message, and then collapse the thread?

No, I just get the mails filtered in a folder, so when There's only one bugmail for one bug on a given date, I only see in the thread pane one email. When I select this email you get the screenshot. Way to get around that is to use the mail veiw widget and select unread.

Comment 8

[Dan Mosedale (:dmosedale, :dmose)]

I'm still not seeing how this bug meets either of these criteria:

a) make the upgrade experience from TB2 very painful for a large number of users

or 

b) be a new, reproducible, severe quality issue (eg dataloss, frequent crashes)

So I'm marking this as blocking- for now.  If things change (i.e. we get feedback from Roland or someone else that this is a common problem), please renominate.  Roland, is this something you've seen many reports of in GS?

That said, I'd still love to see us get this.

Comment 10

[Tim Altman]

I'm seeing this issue in 3.1RC1.  It seems to happen particularly in a thread that already has some messages read, not just unread messages.  My work-around is to temporarily disable threading by clicking the thread icon at the top of the message list.

Comment 11

[Chris Pepper]

I have a very similar problem -- I have one mailbox set to Sort by: Date, Ascending, Threaded; Threads: Threads with Unread. Each time I visit that folder, I see a list of threads (one per line). The disclosure triangle flickered the first time I clicked it, but then turns lighter grey and stops responding. The * key on the keypad (and Shift-8) does nothing. View: Expand All Threads does nothing.

The workaround from comment 10 works -- if I click the swirl column header I see all/only the unread messages, in a flat rather than hierarchical list.

Comment 12

[Wayne Mery (:wsmwk)]

Does this reproduce with mail.operate_on_msgs_in_collapsed_threads set to false?  (which is what I use)

odd. I don't believe I've ever seen this.

Comment 13

[Ludovic Hirlimann [:Usul]]

(In reply to comment #12)
> Does this reproduce with mail.operate_on_msgs_in_collapsed_threads set to
> false?  (which is what I use)
When the value is set to false it works. thanks for the hint wayne. That value is set to true by default.

Comment 14

[Chris Pepper]

I flipped that to false and returned to my problematic IMAP folder, but the disclosure triangle still does not work. I haven't quit & relaunched yet, though.

Comment 15

[Ludovic Hirlimann [:Usul]]

I relaunched when I set it to false.

Comment 16

[Phil Pishioneri]

(In reply to comment #12)
> Does this reproduce with mail.operate_on_msgs_in_collapsed_threads set to
> false?  (which is what I use)

It does not reproduce when set to false.

Comment 17

[Ludovic Hirlimann [:Usul]]

protz could this be a fall out from bug 595654 ?

Comment 18

[Jonathan Protzenko [:protz]]

Don't think so. That bug is only about making sure other extensions don't mess up with the multimessage pane.

CCing Andrew who might have some thoughts on this. Andrew, could it be that the folder display logic cancels some events?

We'll soon have the whole team on CC =).

Comment 20

[Patrick Cloke [:clokep]]

I've also been seeing this bug frequently (I probably run into it daily), when I do click on the expand chevron, I get:
Timestamp: 7/3/2012 7:46:30 AM
Error: Component returned failure code: 0x80550008 [nsITreeView.toggleOpenState]
Source File: chrome://global/content/bindings/tree.xml
Line: 245

This is particularly difficult for me as I don't even use the preview pane so I end up hitting enter and (sometimes for bugmail) opening 30 - 40 tabs of messages.

After flipping mail.operate_on_msgs_in_collapsed_threads to false and restarting, I can easily open the single message, which generally works well enough for me. Thanks for the work around. :)

(In reply to Tim Altman from comment #10)
> It seems to happen particularly in a
> thread that already has some messages read, not just unread messages.
I think I've only ever seen this with a thread that has at least one read message in it, as well as the unread message (e.g. often with bugmail).

Note that I'm seeing this on a current Daily build (16.0a1 (2012-07-02)).

Comment 21

[Ludovic Hirlimann [:Usul]]

Patrick clicking on the unread filter also helps !

Comment 22

[Wayne Mery (:wsmwk)]

Is this still seen in 38 or newer?

Comment 23

[Patrick Cloke [:clokep]]

I haven't seen this anymore, but I'm not entirely sure when I'm supposed to have seen it! I did revert the mail.operate_on_msgs_in_collapsed_threads pref a couple weeks ago to 'try' to reproduce.

Comment 24

[Ludovic Hirlimann [:Usul]]

(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #22)
> Is this still seen in 38 or new

I'm not seeing this but I've switched machines so I might have lost some settings.

Comment 25

[Wayne Mery (:wsmwk)]

Patrick, Would you be able to debug this?

Comment 26

[Patrick Cloke [:clokep]]

I haven't seen this.

Comment 27

[alta88]

Not reproducible either; should be reopened if anyone can.