Closed Bug 196787 Opened 21 years ago Closed 21 years ago

[mailviews] Views based on Status display strange results

Categories

(SeaMonkey :: MailNews: Message Display, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 183158

People

(Reporter: nbaca, Assigned: sspitzer)

Details

(Whiteboard: [adt3])

Trunk build 2003-03-10: Mac 10.1.5
(Cannot try on windows due to bug# 196755)

Overview: Views based on Status do not work as expected

Steps to reproduce:
1. Display the Status column in the thread pane
2. Create a view - "Status" "is" "New", OK (i.e. StatusNew)
3. Close the Customize Message Views dialog
4. Switch to the "All" view, then switch back to the StatusNew view to see the
results in the thread pane

Actual Results: No messages appear in the thread pane

Expected Results: "New" messages should appear

Additional Information: 
Here is a summary of results. In all cases I double checked the View to ensure
that it was defined correctly.
a. "Status" "Is" "New" --> No messages appear yet there are New messages
b. "Status" "Is" "Read" --> Displays Read and Forwarded messages (yet the status
column for the forwarded messages states "Forwarded")
- "Status" "Is" "Forwarded" --> Displays New messages
Marking nsbeta1 because creating a view using the Status settings does not work
as expected.
Keywords: nsbeta1
QA Contact: esther → nbaca
Mail triage team: nsbeta1+/adt3
Keywords: nsbeta1nsbeta1+
Whiteboard: [adt3]
Trunk build 2003-03-28: WinXP with the Modern skin
I'm seeing the same problems as originally reported.
Blocks: mailviews
Related to bug 199464?
dup of 183158 (there were two fixes, but both fixes were checked in under that bug)

*** This bug has been marked as a duplicate of 183158 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Verified Duplicate, and it is now working as expected.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
No longer blocks: mailviews
You need to log in before you can comment on or make changes to this bug.