Closed Bug 20061 Opened 26 years ago Closed 20 years ago

biff timer should fire when mail is launched

Categories

(MailNews Core :: Backend, defect, P3)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: phil, Assigned: sspitzer)

References

(Blocks 1 open bug)

Details

(Whiteboard: [nsbeta3-])

In 4.x and mozilla, the biff timer doesn't fire immediately when you launch mozilla. It waits until the biff interval has elapsed, and then fires. I think the right behavior is for biff to fire when the app launches, and on every interval after that. I assume we'll need some really small startup component to see if we need to run biff when the browser launches, without waiting for a three pane mail window.
QA Contact: lchiang → fenella
Status: NEW → ASSIGNED
Target Milestone: M14
Setting M14
M17
Target Milestone: M14 → M17
Moving to M18 and nominating for beta3.
Keywords: nsbeta3
Target Milestone: M17 → M18
reassigning to gayatrib
Assignee: putterman → gayatrib
Status: ASSIGNED → NEW
Keywords: mail2
nsbeta3- per mail triage review
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
removing mail2 keyword.
Keywords: mail2
Assign it to Sheelar
QA Contact: fenella → sheelar
adding this to biff tracking bug
Blocks: biff
reassigning to racham
Assignee: gayatrib → racham
QA Contact: sheelar → stephend
Is this still an issue? I understand this bug as meaning "Mozilla doesn't check for new mail on startup, but waits until the biff timer has elapsed." If that is correct, then Mozilla does in fact check immediately on startup, for each account that has "Check for new messages at startup" selected in the Server Settings.
mass re-assign.
Assignee: racham → sspitzer
Product: MailNews → Core
Very old bug which has been WFM for some time.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.