Closed
Bug 36092
Opened 25 years ago
Closed 25 years ago
POP: Biff icon should appear in the Folder level
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
INVALID
M17
People
(Reporter: fenella, Assigned: gayatrib)
References
(Blocks 1 open bug)
Details
Linux (2000-04-17-11 M16)
WIn32 (2000-04-17-09 M16)
1. Launch Messenger using -mail option
2. Click on Get Msg to load all new message, mark them all As Read, and make
sure no "unread" message exists and no biff icon exists.
3. Set biff for 1 minute "Check for New Mail for 1 minute" and automatically
download new messages
4. Send a new message to this POP account
5. After 1 minute, I see the new message automatically downloaded and the biff
green diamond appears in the message thread. However...
Actual result: the biff icon green diamond does not show up in the folder level
Expected result: The biff icon should appear in the folder level at this point.
Per Scott P., eventually, biff icon would not appear in the folder pane. Spec
will be changed to reflect this change. But at this point, this is a bug.
This occurs on Linux and WIn32. Mac today's commercial build is not available
yet.
Assign bug to gayatrib and myself.
Assignee: selmer → gayatrib
QA Contact: lchiang → fenella
Mac (2000-04-17-11 M16)
This problem also occurs on Mac as well.
Comment 5•25 years ago
|
||
I think this might be a dup of the uncomfirmed bug Jay Garcia filed.
Anyway, it appears that pop biff is no longer working. Currently you can see
that by the fact that the biff icon shows up next to the folder. So even though
the new spec calls for it not to show up next to the folder, we need to make
sure that pop biff works.
Comment 8•25 years ago
|
||
marking this invalid now. We now want biff to show up at the account level.
There is a bug on this. Bug 24943
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•