If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Search Messages list doesn't have Read/Unread column; can't change Read/Unread status

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
15 years ago
9 years ago

People

(Reporter: Daniel B., Assigned: Navin Gupta)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

In the Search Messages window, the message list table doesn't have
a Read/Unread status column.  This means that users can't mark read 
messages unread (or vice versa) as they can in other lists of messages
(in the regular mail window).

(I believe Netscape 4.x supported this, although I can't confirm that
at the moment.)

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

14 years ago
Wontfix.  See http://www.mozilla.org/mailnews/specs/search/#Mail section C for
the rationale.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Depends on: 107878
Resolution: --- → WONTFIX
(Reporter)

Comment 2

14 years ago
> See http://www.mozilla.org/mailnews/specs/search/#Mail section C for
> the rationale.

That says:

  The unread and flag column are also not available (because any changes 
  to their state would need to be tracked to the other mail windows as well).

That logical is invalid.  Mozilla tracks state and updates other windows
anyway. 

(Try opening two mail windows on different folders.  In one window, drag a 
message from the message list to that windows folder tree view.  Notice how
in the other window the other mail folder's message list is updated.)


Reopening.

Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago12 years ago
Resolution: --- → EXPIRED

Updated

9 years ago
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search
You need to log in before you can comment on or make changes to this bug.