Sheela Ravindran Reporter
	Description • 24 years ago

Buildid:  2001-04-04-12win98

When I was verifying bug 74018, I see that we can now set a limit on message 
download in pop account.  When we exceed the limit there is a message displayed 
in the message pane letting the user know about the message being turncated 
because of the size set in the pref settings.  There is a link 'click here' to 
download the complete message. When I did that we did get the complete message 
from the server but do not refresh the message pane.  
I saw that thread pane changed and got the newer message as unread but I had to 
click on the messsage again on the thread pane to able to display the complete 
message that we got from the server.

Expected: when I clicked on the link to download the complete message from the 
server should also auto display the message in the message.

	Sheela Ravindran Reporter
	Comment 1 • 24 years ago

change qa contact myself. Adding keyword.  Checked with laurel and she said 
that 4.x automatically refreshed the message pane with the complete message.

	laurel
	Comment 2 • 24 years ago

This still exists, and in some cases I'm seeing multiple copies of the full
message copy after retrieval.  Seen on july9 branch with linux rh6.2, seen when
there is only one (truncated) message in the inbox.

	Sheela Ravindran Reporter
	Comment 3 • 23 years ago

*** Bug 105492 has been marked as a duplicate of this bug. ***

	Sheela Ravindran Reporter
	Comment 4 • 23 years ago

Nominating this bug for better user experience.  We should refresh the message 
after getting the whole message and display it in the message pane. Currently 
the message still shows the message truncated warning and does not load the 
complete message. If you keep clicking on the link to download message then you 
can land up with multiple copies of the same message.  

	Sheela Ravindran Reporter
	Comment 5 • 23 years ago

*** Bug 116596 has been marked as a duplicate of this bug. ***

	Sheela Ravindran Reporter
	Comment 6 • 23 years ago

Raising the severity to major since I don't see any milestone on this bug.  This
bug has some odd behavior which is very confusing to the users. 
I would be very glad to see this fixed. We will see more bugs and reports for
each wierd behavior.  Also see bug 118432 and the dup bugs attached to this bug
will describe some odd behavior. I am sure all this should go away when this bug
gets fixed. 

	Navin Gupta Assignee
	Comment 7 • 23 years ago

*** Bug 118432 has been marked as a duplicate of this bug. ***

	Navin Gupta Assignee
	Comment 8 • 23 years ago

I am moving it to 0.9.9 but not sure if I will be able to get to it. 

	Navin Gupta Assignee
	Comment 9 • 23 years ago

The fix is basically to select the message. This should have been caught earlier,
we have made couple of releases since we first converted threadpane to outliner!!

	Navin Gupta Assignee
	Comment 10 • 23 years ago

The fix is to make selectMessage work!

	Navin Gupta Assignee
	Comment 11 • 23 years ago

looks like it was caught but we triaged it 

	Navin Gupta Assignee
	Comment 12 • 23 years ago

cc bienvenu for review. There is a semicolon missing on 1st line but it works

	David :Bienvenu
	Comment 13 • 23 years ago

Comment on attachment 67829 [details] [diff] [review]
proposed fix

r=bienvenu. Should you check if msgHdr is null or not? You should run this by
Seth for an sr too. thx.

	Navin Gupta Assignee
	Comment 14 • 23 years ago

I see only one use of this SelectMessage, only here. I will add a null
check to be extra-safe before checking in. 

	(not reading, please use seth@sspitzer.org instead)
	Comment 15 • 23 years ago

Comment on attachment 67829 [details] [diff] [review]
proposed fix

looks good.  sr=sspitzer

	Navin Gupta Assignee
	Comment 16 • 23 years ago

fixed

	laurel
	Comment 17 • 23 years ago

Will take this one since sheela will be out for awhile

	laurel
	Comment 18 • 23 years ago

This works from the thread pane, but doesn't work properly in standalone message
window.
Will mark this one verified and log standalone window problem separately.
OK using feb21 commercial trunk build: win98, mac OS 10.1, linuz rh6.2

	laurel
	Comment 19 • 23 years ago

Standalone message window issue logged as bug 127100.