Closed
Bug 8362
Opened 25 years ago
Closed 25 years ago
[NEWS] Move newsgroup alerts from console to popup
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M10
People
(Reporter: scurtis, Assigned: sspitzer)
References
Details
(Whiteboard: [PR1])
All platforms, June 16 builds:
From bug 8126:
"try posting to this group: afafafa
Eventually, you'd get an alert that says "A News (NNTP) error occurred:
437 Unwanted newsgroup "afafafa"
But since string bundles and alerts aren't working yet, you'll just see this in
the console window (on Windows and UNIX):
Alert: [StringID -2147467259?]
feel free to log a bug on that."
--------
This is that bug. :-)
Seth, is the fact that the cancel post confirmation just goes to the console,
too (with an enforced "yes" answer), this same bug? Should we make this bug more
general, or would you like a separate one for each popup?
Assignee | ||
Comment 2•25 years ago
|
||
we can leverage this bug. just change the subject.
thanks.
Summary: [NEWS] Move bad newsgroup alert from console to popup → [NEWS] Move newsgroup alerts from console to popup
OK. This bug now contains both listed instances plus any other newsgroup popups.
I don't think we have the functionality yet to need any mail message popups, so
I can't test to see if it affects mail, too...so for now, I'm leaving the
subject newsgroup-specific.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Assignee | ||
Comment 4•25 years ago
|
||
waiting until after necko lands.
marking m9
Assignee | ||
Updated•25 years ago
|
Target Milestone: M9 → M10
Assignee | ||
Comment 5•25 years ago
|
||
moving until m10. alerts and dialogs have been problematic, and I'm told to
wait until necko lands.
Assignee | ||
Comment 6•25 years ago
|
||
this depends on 7770
Sounds like this needs to be fixed by PR1, so I added a note in the Status
Whiteboard
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•25 years ago
|
||
error responses from the server will now show up in alerts.
to test, try posting a message to a non-existant newsgroup.
note: "Alert: [StringID -2147467259?]" will still show up on the console. now,
that's a separate problem, and I've logged that bug. (see #12821)
fixed.
Using 1999100320M10 on win98, I get the pop-up alert as stated in
origninal bug so this platform is fixed. However with 1999100118M10 on linux
and 1999100120 on mac, I don't get the pop-up error. I don't even get the error
string in the console. Note: because of bug 15186 and 15212 it's very tricky
posting to a newsgroup, so I would like to retry on mac and linux when those
bugs are fixed.
Comment 10•25 years ago
|
||
For now, change QA contact to Karen.
Updated•25 years ago
|
OS: Windows 95 → All
Comment 11•25 years ago
|
||
Used 10-08-12-M11 commercial build on all the platforms:
I retested on all the platforms: (Win98/NT, Mac & Linux)
Although the warning dialog: "A New(NNTP) error occured: No such group"
displayed all the platforms. But I have questions for the display timing of this
dialog...
This dialog not displayed right away after I typing the invalid newsgroup and
click OK...it displayed after I subcribed this invalid newsgroup.
And, I need to select the news server and select that "not valid
newsgroup(ex:afafafa)" again to get this warning dialog.
Does this dialog suppose to work this way...???
Comment 12•25 years ago
|
||
I still have the same question as previous comments...
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•25 years ago
|
||
Since this bug is opened for "Move newsgroup alerts from console to popup"...
The warning dialog: "A New(NNTP) error occured: No such group"
already displayed all the platforms...so I will passed by retest for this
bug now.
For this dialog display timing question from the previous comment,
I may log another bug for later milestone if still concern about it. Mark as
Verified.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•