Closed
Bug 127625
Opened 23 years ago
Closed 15 years ago
While read news in offline across groups first message is not displayed
Categories
(SeaMonkey :: MailNews: Backend, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: v.kazmirenko, Unassigned)
Details
I'm reading news in offline mode. After current group is finished I press
'space' or 'n' to get next unread message in next group. New message is selected
in right upper pane, but its content is not displayed in right bottom pane. If I
point any other message and then first selected again it is displayed.
For offline this behavior is always reproducable. Newer occurs for online mode.
If it might help, the same problem I remember from Communicator age. However
there was a shortcut Shift-P to jump previous message and Shift-N to get back.
With Mozilla I have to use mouse. It annoys.
Reporter what build id are you using?
I am using 2002022203 on NT 4.0 and it works for me.
I downloaded few newsgroups, went offline. Then used space bar/n/
next on toolbar to advance to the next mesg in the next newsgroup
and it worked..
Reporter | ||
Comment 2•23 years ago
|
||
I'm using the same 2002022203 on w2k sp2, pIII/128 if it useful. But I would
like to point that described behavior I observe for sveral builds (though can
not reproduce all ID).
Workaround found - View->Reload helps. 'Alt-V', 'R' is not difficult to press,
however there are no pleasure of it...
Reporter still can't reproduce the problem in 2002022703 on NT 4.0
Have you tried a new profile? Does the problem exist for a newly
subscribed/downloaded newsgroup?
Reporter | ||
Comment 4•23 years ago
|
||
Well, I've downloaded 2002022703. The problem remains. It not always appears
with the first newsgroup, but always with second or third.
About new profile. I did not create it for a several years with my Communicator.
That profile i converted to Mozilla. However, I've heard about problem with old
profiles.
So I created fresh profile with only one news group account. I subscribed to 3
newsgroups on news.mozilla.org. Using Download/Sync now I downloaded 20 messages
in each newsgroup. After download been completed Mozilla went offline. I
successfully read first newsgroup, finished it, on the end of the last message
pressed 'n'. Selection jumped to next newsgroup, Subjet of new message was
displayed in a right top plane and on the Subject panel of bottom pane (gray
panel). But message content was not seen in bottom pane. The same orrurs with
the first message in the third newsgroup.
I've tried Classic and Modern theme. The bug appears in all builds I've tried.
I've tried under heavy load and on freshly booted machine with only Mozilla running.
If it may help. I'm running w2k sp2 on pIII-800/128M RAM.
Reporter | ||
Comment 5•23 years ago
|
||
Same behavior with 2002022808.
Reporter | ||
Comment 6•23 years ago
|
||
Same behavior with 2002030703
Using 2002031103 commercial trunk on NT 4.0.
This works for me still.
The only time i see this:
>New message is selected
>in right upper pane, but its content is not displayed in right bottom pane
Is when advancing to next unread mesg (in a new newsgrp) but that new
mesg hasn't been downloaded but it still is marked as new.
Reporter maybe you haven't downloaded all news mesgs? So when you go
offline and advance to next unread mesg that the mesg pane comes up blank
is because the mesg you selected hasn't been downloaded but is new?
Reporter | ||
Comment 8•23 years ago
|
||
Thank you for paying attention to this bug.
I want to clear up the situation. You've suggested, that new message was not
downloaded. But in such case corresponding diagnostic is displayed (The body of
this message has not been downloaded from the server for reading offline and so
on). It is not my case. I'm absolutely sure, that message body is stored
locally. The reason of my assurance is the workarounds that I've discovered.
I've described them above but will repeat.
1) Select another message and then point the first selected again. It will be
displayed.
2) Select menu View->Reload and it will help.
In both cases Mozilla remains in offline mode so it cannot get message from
network. However, I can try unplug LAN cable to ensure ;-)
I've added a comment to another bug
(http://bugzilla.mozilla.org/show_bug.cgi?id=103246) that deals with similar
problem while
reading POP mail. I suggested that mechanism is quite similar - for reading news
in offline and reading pop mail the message body is first stored to disk and
then displayed.
Since the time of report things came a little bit better, now this behavior
occurs in approx. 9 cases of 10. I have a feeling that it just have not enough
time to render.
For statistics: 2002031103 also has the same problem.
Ok. Reporter I can confirm it..
When I posted comment 7, I did see your bug but didn't notice it.
Comment 7:
>Is when advancing to next unread mesg (in a new newsgrp) but that new
>mesg hasn't been downloaded but it still is marked as new.
It should have displayed the mesg "this mesg isn't available..."
But it didn't. So I tried again and Yes I can now reproduce
your bug.
Steps to reproduce:
1. Subscribe to at least 2 newsgroups
2. Select a few mesgs in first grp and download them
by get selected mesgs
3. Go to Menu: Message|Mark|Mark all read
4. Select a few mesgs in 2nd grp and download them
by get selected mesgs
5. Go offline (don't download mesgs at prompt)
6. Go to first newsgrp and select either down or non-down loaded mesg
7. Click N
8. Prompt asks you to advance to next mesg, click OK
Result:
Depending on whether the first new/unread mesg is downloaded or not
in 2nd newsgroup you will see:
non-downloaded mesg - blank mesg pane
downloaded mesg -blank mesg pane
expected : either 'mesg isn't available because you're offline..' or
contents of downloaded mesg body
If you click on any mesg it then snaps back and get mesg body
or not downloaded mesg.
David, what I think happens is when we get prompted to advance
to the next unread mesg in next newgroup it behaves like we
clicked on the newsgroup but haven't actaully selected a mesg in that
newsgrp but we have selected a mesg. As I can't go to the
View|Message Source as it's grayed out.
Marking as new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•23 years ago
|
||
I have noted this problem also in ONLINE mode for quite some time...
Comment 11•22 years ago
|
||
someone recently fixed a bug in this area - can you reproduce this with 1.6b or
thunderbird .4?
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•17 years ago
|
QA Contact: grylchan → offline
![]() |
||
Comment 12•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Updated•16 years ago
|
Assignee: bienvenu → nobody
QA Contact: offline → mailnews-backend
![]() |
||
Comment 13•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•