Open
Bug 741825
Opened 12 years ago
Updated 12 years ago
mark folder read isn't properly stored in mail folder
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: moz, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120329 Firefox/13.0a2 SeaMonkey/2.10a2 Build ID: 20120329013002 Steps to reproduce: 1) Mark folder read on Mailfolder 2) rebuild msf (via properties -> repair folder) Actual results: mark folder read seems to work, all messages in folder are marked read. rebuilding .msf brings previously unread mails back to unread status selecting unread messages and mark them read works as intended Expected results: Mails should keep there status as read
Comment 1•12 years ago
|
||
is there an x-mozilla-status header in the message(s) in question, and does it have the last number set to 1?
Reporter | ||
Comment 2•12 years ago
|
||
I can reproduce this with any mailfolder. All messages have x-mozilla-status headers, but it doesn't change when I mark folder read via contextmenu, x-mozilla-status of the messages stays at 0000, only the display in the threadpane changes from bold to normal and the counter in the folderpane is changed.
Comment 3•12 years ago
|
||
Tony can you reproduce?
Comment 4•12 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #3) > Tony can you reproduce? Yes I can, as follows: 1. Go to Trash folder 2. In Folders pane, Right-click → Mark Folder Read -- All messages in Threads pane are now shown in unbold type 3. In Folders pane, Right-click → Properties → Repair folder -- All messages in Threads pane are now shown in bold type. My custom is to mark messages as unread immediately before moving them to Trash using Right-click → Move to… Using the following build: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 ID:20120627003020 http://hg.mozilla.org/mozilla-central/rev/5cdbeae14405 http://hg.mozilla.org/comm-central/rev/2a7420635947
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in
before you can comment on or make changes to this bug.
Description
•