Closed Bug 14106 Opened 25 years ago Closed 24 years ago

View|Messages|* does not work

Categories

(MailNews Core :: Backend, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: fenella, Assigned: sspitzer)

References

Details

Linux (1999-09-16-09 M11)
Win_nt 4.0 (09-16-09 M11)
Mac (1999-09-16-08 M11)
1. From Messenger, select Inbox, I have several Unread messages (status shows
green diamond)
2. Select View|Messages|Unread,
Actual result: Nothing happens. In the console window of the Linux and the
Win_nt, an error message is displayed:
gViewUnreadMsgsJavaScript Error: view is not defined
URL: chrome://messenger/content/widgetglue.js
LineNo: 203
Expected result: Only Unread messages should be displayed in the thread pane.
This happens to all 3 platforms.
Assignee: phil → putterman
Summary: View|Message|Unread does not work → [FEATURE] View|Message|* does not work
Target Milestone: M15
Reassign to putterman, TFV M15. Also generalized subject to indicate that no
View|Messages options are expected to work right now.
Blocks: 10791
QA Contact: lchiang → fenella
add to feature tracking bug.
*** Bug 17260 has been marked as a duplicate of this bug. ***
Target Milestone: M15 → M16
Status: NEW → ASSIGNED
Using Dec15 commerical builds on all platforms:
I noticed a nasty side issue with View|Message|Unread:
If you try using View Unread, it won't take effect on the current/selected
folder (we know this). HOWEVER, when you switch to other (I'm using IMAP)
folders which are indeed populated (but have no unread), they will not load the
thread pane -- I'm assuming it's trying to invoke the Unread view. Once in this
state, you must do a View|Message|All in order to get the thread pane to load in
any folders but the initial one (inbox) you did the View Unread on.  Ick.
In the Menu item View|Message|Mark|As Unread, the dot "." has been removed,
which means this menu suppose to work, right?
Anyway using Linux and Mac (2000-01-12-08 M13), and Win32 (2000-01-12-11 M13),
this problem is still there.
This bug describes behavior related to the View|Messages menu where it displays 
the Unread and Read options. The Summary of this bug should actually change to 
state "[FEATURE] View|Messages|* does not work".

Another bug should be opened for "[FEATURE] View|Message does not work" 
explaining that this item will open the current message in a new window.

If this sounds ok then I can make the changes or if someone else wants to make 
the changes then that's fine too.
Go ahead and clarify and make changes, Ninoschka.
Changing Summary to "View|Messages|* does not work".
Summary: [FEATURE] View|Message|* does not work → [FEATURE] View|Messages|* does not work
Priority: P3 → P2
Whiteboard: 1 week
marking as P1, at least the View|Messages|Unread part.
Priority: P2 → P1
this got rejected by PDT.  We still need to do threads with unread and the 
unread view in threaded mode.  I want to hold onto this bug for a possible 
intern project. So I'm moving to M20 and removing feature to make it not show up 
on PDT's radar.
Summary: [FEATURE] View|Messages|* does not work → View|Messages|* does not work
Whiteboard: 1 week
moving to M21 to hold onto this and get it off radar.
Target Milestone: M16 → M21
changed my mind. Moving to future milestone.
Target Milestone: M21 → Future
Bug 45252 has been written to remove menu items
nominating for mail3
Keywords: mail3
reassigning to sspitzer
Assignee: putterman → sspitzer
Status: ASSIGNED → NEW
adding nsbeta1- keyword.  We'll eventually get to a place where this can work,
but things like making threads behave correctly need to be improved first.
Keywords: nsbeta1-
Worksforme on Windows98. Build 2001011004.
Linux (2001-01-11-06 mtrunk)
Win32 (2001-01-11-06 mtrunk)
Mac (2001-01-11-04 mtrunk)
The View|Messages|* options are now working on these build.

Seth, should this be marked Worksforme or Fixed?

fixed when "threads with unread" got implemented.

marking fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verify it.
Status: RESOLVED → VERIFIED
*** Bug 60852 has been marked as a duplicate of this bug. ***
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.