Phil Peterson Reporter
	Description • 25 years ago

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.

	scottputterman
	Comment 1 • 25 years ago

Setting M14

	Phil Peterson Reporter
	Comment 2 • 25 years ago

M17

	scottputterman
	Comment 3 • 24 years ago

Moving to M18 and nominating for beta3.

	scottputterman
	Comment 4 • 24 years ago

reassigning to gayatrib

	lchiang
	Comment 5 • 24 years ago

nsbeta3- per mail triage review

	scottputterman
	Comment 6 • 24 years ago

removing mail2 keyword.

	fenella
	Comment 7 • 24 years ago

Assign it to Sheelar

	Sheela Ravindran
	Comment 8 • 24 years ago

adding this to biff tracking bug 

	scottputterman
	Comment 9 • 24 years ago

reassigning to racham

	Mike Cowperthwaite
	Comment 10 • 22 years ago

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.

	(not reading, please use seth@sspitzer.org instead) Assignee
	Comment 11 • 22 years ago

mass re-assign.

	Mike Cowperthwaite
	Comment 12 • 19 years ago

Very old bug which has been WFM for some time.