Closed Bug 365016 Opened 18 years ago Closed 17 years ago

Viewing in message pane for messages in newsgroup not always possible

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: omar.bajraszewski, Assigned: mscott)

References

Details

(Keywords: verified1.8.1.4)

Attachments

(3 files)

Screenshot of the problem
27.92 KB, image/jpeg
Details
proposed fix
900 bytes, patch
mscott
: superreview+
Details | Diff | Splinter Review
Problem is not gone
58.46 KB, application/x-shockwave-flash
Details 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

I subscribe a few newsgroups. When I select them and want to preview a message it's not always possible

Reproducible: Sometimes

Steps to Reproduce:
1.Subscribe to 2 or more newsgroups
2.Click on a newsgroup to download messages
3.Select a message to preview it

Actual Results:  
1.Preview is not available. Selecting any message gives the same result
2.Resolution: click on another newsgroup and then again on previous newsgroup---> preview is again possible

Expected Results:  
Preview is always possible

Layout: Classic view, message pane is enabled

version 2 beta 1 (20061225)
I get this occasionally, haven't found out how to reproduce.
OS: Windows XP → All
Hardware: PC → All

    
    

    
  
As you can see mail is focused but preview is not available. I can't see any errors in console. Still I don't know how to reproduce it

    
    

    
  
This does the same thing with email folders. All you have to do is click on some other folder, then click back on the one you want to view. 

    
    

    
  
Confirming.

Here's a video of my experience with this bug. 
<http://ilias.ca/flashback/tb-newsbug.html>
In my cases, there's a message in the message pane (probably a cached version or a result of mailnews.remember_selected_message=2), but clicking on another message has no affect on the message pane.
Status: UNCONFIRMED → NEW
Ever confirmed: true

    
    

    
  
With which version do you see this? (I have a feeling the problem has gone away sometime after beta1...) And I suppose you don't have a way to reproduce?

    
    

    
  
I can't locate the bug I'm thinking of right now, but there was (still is?) something about selecting a folder when an account node had been selected previously.  The workaround was to hide, then re-display, the message pane (e.g. hit F8 twice).  If reporters here are still seeing this problem, state here whether that workaround fixes it.

I know that problem wasn't entirely fixed -- if you don't have "remember last message" selected, select an account, then select a folder with a lot of messages, the folder doesn't scroll all the way to the end of the sort like it's supposed to.  But I think the problem of not being able to load a message into the message pane has been fixed; I just can't find the bug.
Summary: Preview for messages in newsgroup not always possible → Viewing in message pane for messages in newsgroup not always possible

    
    

    
  
(In reply to comment #6)
> With which version do you see this? (I have a feeling the problem has gone away
> sometime after beta1...) And I suppose you don't have a way to reproduce?
> 

Well, I saw the problem three days ago ( I keep updating Thunderbird to latest version every day). But it doesn't happen as often as it used to.

    
    

    
  
I see this as occasionally as well, most recently with nightly Thunderbird 2.0 beta 2 20070213 on Linux. Double clicking on the message displays the message contents in a new window. After closing the window, normal message viewing works.


    
    

    
  
The "hitting F8 twice" suggestion doesn't work for me.

    
    

    
  
(In reply to comment #10)
> The "hitting F8 twice" suggestion doesn't work for me.

Yeah, I know -- after I posted comment 7, I started running into this bug myself, and it's definitely something different.  Alas, Bugzilla doesn't allow one to mark one's comment as 'worthless'.

    
    

    
  
I've been backtracking through Thunderbird 2 nightlies, and as far as I can tell Thunderbird/2.0b1pre ID:2006092304 is the first Tb2 nightly to have this bug. I've been trying my darnedest to reproduce this in 2006092204, and haven't.

Scott, any check-ins at that time, you think might be the cause of this bug?

    
    

    
  
Bug 353689?  That's a shot in the dark, but the only Mailnews checkin that Bonsai Watch reports on that day.

    
    

    
  
The only thing I could find is bug 275199.

    
    

    
  
My apologies. I came across this in 2006092204. I'll keep backtracking.

    
  
Flags: blocking-thunderbird2?

    
    

    
  
I'm as far back as Thunderbird/2.0a1 ID:2006090606, and still see this; but I just had a thought:
How many people experiencing this have the Enigmail add-on installed?

    
    

    
  
I do not have Enigmail installed, but I hit this frequently.

    
    

    
  
I experience the problems and I have Enigmail installed. That is, with the contents of email folders not being displayed if clicked until a different folder is first clicked, then it is displayed as normal.

    
    

    
  
(In reply to comment #19)
> How many people experiencing this have the Enigmail add-on installed?

I don't use Enigmail but I can still see the problem


    
    

    
  
I have precisely this behavior in TB version 2 beta 2 (20070116). the only add-ins I have are Lightning 0.3.1, british Dictionary, Webmail 1.0.15, Webmail-Hotmail 1.0.16 and Signature Switch 1.4.2

    
    

    
  
bug may go back as far as 20051025 as documented in bug 320301. *If* 320301 is still valid then I suggest 320301 be made a blocker, because the description does not indicate any problem with reading messages that are listed. Also good info in Bug 353984 and others that it mentions

Chris, did you go back further than 2006092204?

does this happen in TB 1.5?  If it does, did it get worse in TB 2??   (I've seen it forever, so I can't tell)

Are there possible causes other than focus or article number?

Additional workaround - do something to reread the message, like "save" message as file.

And there is Bug 362500 (which may be not related, or may even be gone)

    
    

    
  
(In reply to comment #23)
> I have precisely this behavior in TB version 2 beta 2 (20070116). the only
> add-ins I have are Lightning 0.3.1, british Dictionary, Webmail 1.0.15,
> Webmail-Hotmail 1.0.16 and Signature Switch 1.4.2
> 

And the same behaviour does not seem to apply to TBird 1.5 - at least not here....



    
    

    
  
I have encountered this with regards to email, not newsgroups. And that is in Thunderbird 1.5.0.x on Windows XP SP2

    
    

    
  
(In reply to comment #24)
> Chris, did you go back further than 2006092204?

The earliest build I've seen this in so far is Thunderbird/2.0a1 ID:2006080105. I'm currently testing Thunderbird/2.0a1 ID:2006070106. I only noticed it in September; and I had started using Tb2 nightlies in mid-June. 

    
    

    
  
I don't know whether this is part of this bug or something different, , but if you add the "Mark" button to the toolbar, it seems (here at least) to exhibit the same behaviour, ie you need to switch to another group and back again to enable the "Mark" button....

    
    

    
  
Moving off bugs that didn't make the deadline for Thunderbird 2. 
Flags: blocking-thunderbird2? → blocking-thunderbird2-

    
    

    
  
I'd like to do some support site updates for Tb2; but if this bug isn't blocking the release, I'm going to need to start using the latest Tb2 builds, instead of backtracking. If someone else is willing, please feel free to continue backtracking. The earliest build I saw this in is Thunderbird/2.0a1 ID:2006070106.

    
    

    
  
Chris, any JS errors in the console when this happens? 

I see you have some extension based on your screen shot, if you run in safe mode, do you still run into it?

    
    

    
  
Actually, the screenshot is not mine. :-) During testing, I've had Baspage 0.8.0.1, ConfigDate 0.3.9, Conquery 1.6.6, Launchy 4.2.0, MagicSLR 1.2.2, MessageID-Finder 2.0.0, Mnenhy 0.7.5, Nightly Tester Tools 1.1, and QuoteColors 0.2.7. I wasn't using Mnenhy, when I first came across this bug, and created <http://ilias.ca/flashback/tb-newsbug.html>. I'll disable what I can do without, and check the JS console, next time this occurs.

    
    

    
  
Chris, you do not see the problem in 2006070106?  (comment 15)

I don't believe this is related to any extension.  
possible related bugs 
 bug 362500    	
 bug 301211
 bug 319971


    
    

    
  
(In reply to comment #33)
> Chris, you do not see the problem in 2006070106?  (comment 15)

scratch my question ... you do see it there.

this is a common occurrence for me. It was only a quick test, but I do not see it so far in version 3 alpha 1 (20060602)


    
    

    
  
I'm running only with DOM Inspector and Talkback for extensions.  The typical occurrence of this problem for me runs like this:
- Expand the Mozilla News account node; newsgroup nodes update with new counts
- Click on mozilla.support.thunderbird; read messages here with no problem
   (I read very selectively, using the mouse to pick the first message in 
    whichever thread is of interest; I'll use N to step thru the thread, along
    with R and K.)
- Click on mozilla.dev.apps.thunderbird
- Click on a message of interest.  Oh, it's not loading.
- Click on another newsgroup, click back to m.d.a.t
- Click on the message again: loads

I'd say 80% or more of the times I've encountered this, it's in the second newsgroup I enter.  And since I'm restarting TB all the time, there's a high probability that it's the first time I've tried to read news at all in the current session.

    
    

    
  
No messages occur in the console.

    
    

    
  

      
      
      
      

        Attached patch
          
          
        proposed fix
        — 
          — Splinter Review
      

    


  
Scott said he saw this problem, and we were failing in this method because mDatabase was null. I think this would fix it. I haven't tested it, though, because I can't reproduce the problem.

        Attachment #259382 -
        Flags: superreview?(mscott)

    
  

        Attachment #259382 -
        Flags: superreview?(mscott) → superreview+

    
    

    
  
I've landed this fix on the trunk. If you can try tomorrow's trunk build and let me know if it fixes the problem for you, then we could try to get this into 2.0...thx!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED

    
    

    
  
(In reply to comment #38)
> I've landed this fix on the trunk. If you can try tomorrow's trunk build and
> let me know if it fixes the problem for you, then we could try to get this into
> 2.0...thx!

seems to be gone. 1.5yr old bug 301211, labeled as a regression and almost certainly related, should also be tested

major annoyance for reading news so yes, this should go into 2.0.  

Blocks: 301211

    
    

    
  
landed for 2.0, thx for trying this on the trunk, Wayne!
Keywords: fixed1.8.1.4

    
    

    
  

      
      
      
      

        Attached file
          
        Problem is not gone
        — 
      

    


  
I can still reproduce the problem with version 2.0pre (20070323)

    
    

    
  
I checked the change into 2.0 five minutes ago so I don't think it's in the build you tried, unless you pulled and built it yourself :-)

    
    

    
  
Ok, I will try again later :-)

    
    

    
  
I don't see the second symptom listed in the bug #335097 fixed in the thunderbird 2.0pre (20070324). Question: should I report that symptom as a separate bug?

    
    

    
  
Bug 335097 comment 5:
> Second issue looks like bug 263724.

    
    

    
  
ok. I cannot reproduce the bug since the patch was checked-in. Marking as verified (2.0.0.0 (20070326))
Status: RESOLVED → VERIFIED

    
    

    
  
I was not able to reproduce this issue with 2.0 or a recent 2.0 nightly, but based on the last comment, I am marking this v.fixed for the 1.8 branch.
Keywords: fixed1.8.1.4 → verified1.8.1.4

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: