Closed Bug 123910 Opened 23 years ago Closed 20 years ago

Get Next 500 news messages shouldn't be displayed when server selected.


(SeaMonkey :: MailNews: Message Display, defect)

Not set


(Not tracked)



(Reporter: rob.wilcox1, Assigned: Stefan.Borggraefe)


(Keywords: verified1.7)


(1 file)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020406

With the newsgroup server selected, the File->Get next 500 news message option
is available, but doesn't do anything.

I figure that this shouldn't be displayed at this point.. It should only be
displayed when an actual newsgroup is selected.

Reproducible: Always
Steps to Reproduce:
1. Open Mail & Newsgroups.
2. Click the newsgroup server at the top of left of the window
3. Click the File menu, you will then see the  menu item displayed.

Actual Results:  The menu item "Get next 500 news messages" is displayed, but
doesn't do anything.

Expected Results:  Maybe it shouldn't be displayed at this time?
you mean it should not be enabled? Again, a front end issue...
Component: Offline → Mail Window Front End
Ever confirmed: true
That's right.  I don't think it should be displayed, because clicking it doesn't
appear to do anything at all.
Thx Rob
adding stephend
Rob, Gary; this seems to be a DUP of bug 113414.  Please mark it if you agree,
and I'll verify.
No, I don't think it is the same.  What I'm saying is that when you click on the
newsgroup server at the top of the list of newsgroups, then the menu item is
still available.  Is it supposed to be?  When I clicked it, it didn't do anything.
Thx Rob
Okay, server vs. newsgroup, my bad.  
Summary: Get Next 500 news messages displayed always → Get Next 500 news messages shouldn't be displayed when server selected.
fwiw, 4.x disables get next 500 mesgs when server is selected.
Gary how do you mean 4.x ?
The old netscape communicator browser, currently at version 4.79.
Okay, I see.  Then yes, it should not be dispayed as per Communicator  - at
least that's what I think.
Should be Seth's, but maybe Sean Su should help?
Assignee: bienvenu → sspitzer
s/should/could, *really* (not a slip of tongue, fingers, rather).
I have a patch for this.
Assignee: sspitzer → Stefan.Borggraefe
OS: Windows 2000 → All
Hardware: PC → All
Attached patch PatchSplinter Review
Fixes both TB and Seamonkey. This also removes an "else after return" in the
function I touched.
Attachment #145633 - Flags: review?(bienvenu)
Attachment #145633 - Flags: review?(bienvenu) → review+
Attachment #145633 - Flags: superreview?(mscott)
Attachment #145633 - Flags: superreview?(mscott) → superreview+
Comment on attachment 145633 [details] [diff] [review]

Fairly low-risk patch to fix UI nit.
Attachment #145633 - Flags: approval1.7?
Closed: 20 years ago
Resolution: --- → FIXED
Comment on attachment 145633 [details] [diff] [review]

a=asa (on behalf of drivers) for checkin to 1.7
Attachment #145633 - Flags: approval1.7? → approval1.7+
Keywords: fixed1.7
Verified as fix on latest 1.7 branch 06-24 build.
Changing keywords from fixed1.7 to verified1.7.
Leave this bug status "as is" until this bug be verified on trunk again...
Keywords: fixed1.7verified1.7
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.