41977 - UI defaults with download_on_biff ON, biff OFF. UI work needed.

Status: VERIFIED DUPLICATE of bug 63992

(SeaMonkey :: MailNews: Message Display, defect, P2)

Description

[laurel]

Using 2000-06-08 m17 commercial build

UI issue needs to be resolved concerning the pref in Account Settings Server
(POP only?) panel for download_on_biff (automatically download new messages).
This pref is directly related to mail notification (biff).

A new 6.0 profile/account server panel has the main biff pref default state as
disabled, but the download_on_biff pref enabled. This should not be.

The download_on_biff option should be tied to the biff pref.  UI handling in 4.x
varied among the different platforms.

1.  Create a new POP profile or new POP account.
2.  From mail window, Edit|Account Settings.  Select the account/Server panel
for the new POP account.
3.  Notice the default state for "Check for new messages every N minutes" is
disabled.  Notice the default state for "Automatically download any new
messages" is enabled.

Win32 4.x solution was to dim/grey the download new messages option regardless
of its enabled state if the main biff pref was disabled.

Comment 1

[laurel]

cc jglick for any ui/spec relevant input

Comment 2

[jglick]

"Automatically download any new messages" is a sub widget of "Check for new 
messages every X minutes" and hence should only be enabled if its parent 
widget is enabled/check.  Otherwise, it should be disabled/grey. 

I'll made a note in the spec. 

Comment 3

[scottputterman]

moving to M18 as polish.

Comment 4

[sol]

Added "nsbeta3" and "correctness" keywords.

Comment 5

[lchiang]

nsbeta3- per mail triage review. Assuming that biff is off regardless of what 
download on biff setting is.

Comment 6

[laurel]

To answer Lisa's assumption, yes, the last time I checked (awhile ago), biff was
indeed enabled even though the sub-option showed as enabled in ui.  Correct biff
behavior, bad visual display in prefs.

Comment 7

[scottputterman]

marking nsbeta1+

Comment 8

[scottputterman]

moving to mozilla0.8 milestone.

Comment 9

[scottputterman]

reassigning to racham.

Comment 10

[Matthew T (active 1999-2002)]

Hakan, did you file a dup of this earlier?

Comment 11

[Håkan Waara]

I'm not sure. But the bug *is* however in some way related to my fix in bug
63992. Please check it out and reopen if needed.

Comment 12

[scottputterman]

moving to mozilla0.9

Comment 13

[fenella]

Assign it to Sheelar

Comment 14

[scottputterman]

this looks like a dup since the bug is fixed now.  

*** This bug has been marked as a duplicate of 63992 ***

Comment 15

[Sheela Ravindran]

verifying as dup