Closed
Bug 41977
Opened 24 years ago
Closed 24 years ago
UI defaults with download_on_biff ON, biff OFF. UI work needed.
Categories
(SeaMonkey :: MailNews: Message Display, defect, P2)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
mozilla0.9
People
(Reporter: laurel, Assigned: racham)
Details
(Keywords: polish, Whiteboard: [nsbeta1+])
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.
"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.
nsbeta3- per mail triage review. Assuming that biff is off regardless of what download on biff setting is.
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
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•24 years ago
|
||
marking nsbeta1+
Comment 10•24 years ago
|
||
Hakan, did you file a dup of this earlier?
Comment 11•24 years ago
|
||
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 14•24 years ago
|
||
this looks like a dup since the bug is fixed now. *** This bug has been marked as a duplicate of 63992 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: nsbeta3
Resolution: --- → DUPLICATE
Whiteboard: [nsbeta3-][nsbeta1+] → [nsbeta1+]
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•