Closed
Bug 282010
Opened 20 years ago
Closed 19 years ago
Messages for offline use are not downloaded when reading news online
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla.spam2, Assigned: Bienvenu)
References
Details
(Keywords: regression, Whiteboard: required for bug 166111)
Attachments
(2 files)
930 bytes,
patch
|
mscott
:
superreview+
sspitzer
:
approval1.8b+
|
Details | Diff | Splinter Review |
2.02 KB,
patch
|
mscott
:
superreview+
sspitzer
:
approval1.8b+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050210 I have selected several news groups for offline use. Normally I sync the news groups before reading. In this case messages are downloaded from news server correctly. Compared to former builds reading the same news groups online the messages are not downloaded while reading for later offline use anymore. Reproducible: Always Steps to Reproduce: 1. Select a news group for offline use. 2. Open this news group while online. 3. Select a new message. 4. Switch to offline. 5. Try to read the former selected message again. Actual Results: Message body is not downloaded. Expected Results: Message body should be readable. Same happens in recent Thunderbird trunk builds.
Comment 1•20 years ago
|
||
(In reply to comment #0) > Compared to former builds reading the same news groups online the messages are > not downloaded while reading for later offline use anymore. So this is a regression then? What was the last build, where this didn't occour?
Reporter | ||
Comment 2•20 years ago
|
||
This regressed between 2005020406 and 2005020522.
Updated•19 years ago
|
Keywords: regression
Assignee | ||
Comment 3•19 years ago
|
||
recreated this.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: blocking1.8b?
Comment 4•19 years ago
|
||
major feature breakage. adding blocking flag.
Flags: blocking1.8b? → blocking1.8b+
Assignee | ||
Comment 5•19 years ago
|
||
the line passed to NotifyDownloadedLine now contains the native line terminator, so we need to account for that.
Attachment #174322 -
Flags: superreview?(mscott)
Attachment #174322 -
Flags: approval1.8b?
Updated•19 years ago
|
Attachment #174322 -
Flags: superreview?(mscott) → superreview+
Comment 6•19 years ago
|
||
Comment on attachment 174322 [details] [diff] [review] proposed fix a=sspitzer
Attachment #174322 -
Flags: approval1.8b? → approval1.8b+
Assignee | ||
Updated•19 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•19 years ago
|
||
Sorry to bother you... could it be that this patch broke download/sync of news messages? With build 2005021503 messages are downloaded again while reading but download/sync for offline use is broken. If I should file another bug please let me know.
Assignee | ||
Comment 8•19 years ago
|
||
yikes, yes, argh, sorry.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•19 years ago
|
||
downloading for offline also needs to get the linebreak from readnextline, and check for the last line differently. That was the only other caller of NotifyDownloadLine, so this should fix it all.
Attachment #174400 -
Flags: superreview?(mscott)
Reporter | ||
Comment 10•19 years ago
|
||
There is another problem that I just realized. Perhaps this will also be fixed with the new patch. I had some messages in my database that were not displayed after syncing. Checking them in the database file I found out that they were written in a single line to the file without any linke break like this: Path: uni-berlin.de!not-for-mailFrom: xxx xxx <xxx@xxx.xxx>Newsgroups: x.x.x Viewing the source in Messenger the line breaks were displayed but not in an external editor.
Assignee | ||
Updated•19 years ago
|
Attachment #174400 -
Flags: approval1.8b?
Comment 11•19 years ago
|
||
Comment on attachment 174400 [details] [diff] [review] fix for regression pieces of this patch are from bug #107776, which also happens to be a=sspitzer for 1.8b2
Attachment #174400 -
Flags: approval1.8b? → approval1.8b+
Updated•19 years ago
|
Attachment #174400 -
Flags: superreview?(mscott) → superreview+
Assignee | ||
Comment 12•19 years ago
|
||
yes, the line ending problem was the problem.
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•19 years ago
|
Attachment #174322 -
Flags: approval1.7.9?
Assignee | ||
Comment 13•19 years ago
|
||
Comment on attachment 174400 [details] [diff] [review] fix for regression this is fallout from bug 166111, so if we want that, we'll need this fix as well.
Attachment #174400 -
Flags: approval1.7.9?
Updated•19 years ago
|
Updated•19 years ago
|
Component: MailNews: Offline → MailNews: Backend
Product: Mozilla Application Suite → Core
Comment 14•19 years ago
|
||
Not enough components in Core :-( but I need to move this so I can get thunderbird-blocking flags as well.
Flags: blocking-aviary1.0.5?
Comment 15•19 years ago
|
||
If we're going to take this on the stable branches we need to land early in a release cycle. Moving nomination to 1.0.6
Flags: blocking1.7.9?
Flags: blocking1.7.9-
Flags: blocking1.7.10?
Flags: blocking-aviary1.0.6?
Flags: blocking-aviary1.0.5?
Flags: blocking-aviary1.0.5-
Comment 16•19 years ago
|
||
Comment on attachment 174322 [details] [diff] [review] proposed fix 1.7.9 has already shipped. unsetting approval request.
Attachment #174322 -
Flags: approval1.7.9?
Comment 17•19 years ago
|
||
Comment on attachment 174400 [details] [diff] [review] fix for regression unsetting approval 1.7.9 request since that release has already shipped.
Attachment #174400 -
Flags: approval1.7.9?
Updated•19 years ago
|
Flags: blocking1.7.11? → blocking1.7.11-
Updated•19 years ago
|
Flags: blocking1.7.12?
Updated•19 years ago
|
Flags: blocking1.7.13?
Flags: blocking1.7.13-
Flags: blocking-aviary1.0.8?
Flags: blocking-aviary1.0.8-
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•