Open
Bug 482492
Opened 16 years ago
Updated 2 years ago
Feedback/Alert notifications need category information
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
NEW
People
(Reporter: standard8, Unassigned)
References
(Blocks 1 open bug)
Details
At the moment the feedback/alert notifications only have the information that
is in the error message, e.g. "Failed to connect to server xxx".
We need some sort of category/classification of what the errors/messages are so that alerts can be appropriately displayed.
Flags: blocking-thunderbird3+
Reporter | ||
Updated•16 years ago
|
Whiteboard: [b3ux]
Reporter | ||
Updated•16 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Updated•16 years ago
|
Whiteboard: [b3ux] → [b3ux][m4]
Reporter | ||
Comment 1•16 years ago
|
||
David (Ascher) do we want this for poptarts, or should we move it to wanted?
Whiteboard: [b3ux][m4] → [b3ux][m4][still blocking?]
Reporter | ||
Updated•16 years ago
|
Whiteboard: [b3ux][m4][still blocking?] → [b3ux][m5][still blocking?]
Reporter | ||
Updated•16 years ago
|
Whiteboard: [b3ux][m5][still blocking?] → [b3ux][m6][still blocking?]
Updated•16 years ago
|
Summary: Feedback/Alert notifications need category information → [poptarts] Feedback/Alert notifications need category information
Reporter | ||
Updated•16 years ago
|
Priority: -- → P5
Reporter | ||
Comment 2•16 years ago
|
||
Still not sure if I need this for some other bugs. Moving out to b4 for now though.
Whiteboard: [b3ux][m6][still blocking?]
Target Milestone: Thunderbird 3.0b3 → Thunderbird 3.0b4
Reporter | ||
Updated•16 years ago
|
Summary: [poptarts] Feedback/Alert notifications need category information → Feedback/Alert notifications need category information
Reporter | ||
Comment 3•15 years ago
|
||
Whilst we need probably need this at some stage for alerts, it isn't actually blocking any current Thunderbird 3 work, therefore taking off of the blocking list.
Flags: blocking-thunderbird3+ → blocking-thunderbird3-
Target Milestone: Thunderbird 3.0b4 → Future
Reporter | ||
Updated•15 years ago
|
Assignee: bugzilla → nobody
Priority: P5 → --
Target Milestone: Future → ---
Comment 4•15 years ago
|
||
This is a mass change. Every comment has "assigned-to-new" in it.
I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
Comment 5•2 years ago
|
||
Mark, if this is still a valid bug, can you elaborate please - what classifications you foresee, and how it would affect their display ?
Flags: needinfo?(standard8)
Reporter | ||
Comment 6•2 years ago
|
||
Probably more information like "could not contact server" vs "your password is out of date" or something...
Flags: needinfo?(standard8)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•