Closed Bug 21084 Opened 25 years ago Closed 24 years ago

[FEATURE]UI: Need to improve the menu for adding get next/previous x message for newsgroup

Categories

(MailNews Core :: Backend, defect, P3)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 16336

People

(Reporter: huang, Assigned: sspitzer)

Details

All platforms 12-07-08/09 M12 commercial build:

Shouldn't subscribe the new newsgroup directlly when newsgroup messages are over
than 500.

Since there were bug#17795 "NNTP/IMAP subscribe dialog" & bug#16568 "download
headers dialog" features not implement yet. So right now, if subscribe for new
newsgroup even over than 500 still subscribe 500 directlly which is wrong....
Summary: Shouldn't subscribe the new newsgroup directlly when newsgroup messages are over than 500 → [FEATURE]Need to improve the menu for adding get next/previous x message for newsgroup
Since there was a bug#16568 "download headers dialog" features

After talked to Phil & Seth.
Change the summary to improve the file menu to add the get Next or Previous "x"
messages (x based on the no. setting from the preference for the newsgroup.
Assignee: phil → sspitzer
Target Milestone: M17
Summary: [FEATURE]Need to improve the menu for adding get next/previous x message for newsgroup → [FEATURE]UI: Need to improve the menu for adding get next/previous x message for newsgroup
QA Contact: lchiang → huang
[FEATURE] bugs past M16 are OUT for this release.  Marking M20.  If you disagree 
with this action, please help me explain it to the PDT.
Target Milestone: M17 → M20
So, does it mean the "get next x messages" for newsgroup won't be in Netscape 6 
Release? (it used to be in Communicator 4,x....)
Cc: laurel, how do you think for without this feature in Netscape 6?
Yes, it means that feature won't be in.  We shouldn't have any UI which 
reference it.  Do we?
No, I don't think this means the feature won't be in... 
This bug deals with improving the ui wording, which is moved out. In my opinion,
I don't think improving the wording is top importance for this release.
The "feature" itself (and I think we should have that) is covered in feature bug
#16336, which is listed as M17. 
Actually, I log this bug originally for feature itself (not for wording). 
I think maybe the summary I put misleading peoples.
I am just marking this bug dup of bug 16336 and will add [FEATURE]on bug 16336.

*** This bug has been marked as a duplicate of 16336 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Target Milestone: M20 → M17
Verified as duplicate.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.