Closed Bug 45722 Opened 25 years ago Closed 24 years ago

Account Settings: POP Server: UI clean up

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
Future

People

(Reporter: jglick, Assigned: hwaara)

References

()

Details

Account Settings dialog, POP Server panel Minor UI clean up from Mail UE review: 1. Would be nice to have the ability to edit the server name (P4). 2. Group box around server options (P3) 3. Checkbox: "Automatically download any new messages". Child checkbox should be disabled if the parent dialog is not checked. (P3) 4. "use secure connection", U should be capitalized. Remove period (.) from end of sentence. (P5) 5. "Local" label should be moved a touch to the right over its text box (P5). 6."Delete messages on server when...". Isn't this supposed to be a child of "Leave messages on the server" instead of at the same level? 7. Is SSL pref supposed to be here? I seem to recall this item being cut? 8. "Local directory" should say "Local mail directory". (P5) 9. Should the "Local directory" be editable? In 4.x the text field is not editable but their is a "Choose" button.
nominate as b3mail
Keywords: b3mail
QA Contact: lchiang → nbaca
change b3mail to nsbeta3.
Keywords: b3mailnsbeta3
Status: NEW → ASSIGNED
Whiteboard: Partial fix in hand
Target Milestone: --- → M18
Just checked in some fixes: #1 is in another bug #4 is fixed #5 is fixed #6 I don't know about this actually. We need to talk to bienvenu or jefft. #7 nope, so taken out for POP #8 probably WONTFIX because this string is shared amongst all protocols #9 Yes, it should be editable, but it needs a choose button. so all we have left are: #2 #3 #6 (still open issue) #9
Keywords: mail4
Adding mail4 triage nomination keyword.
+ per mail triage for jennifer's P3 or higher items.
Whiteboard: Partial fix in hand → [nsbeta3+] Partial fix in hand
Adding myself to cc: list.
I think this is "good enough" for beta3. Removing nsbeta3 statuses and futuring. If anyone objects, speak now or forever hold your peace.
Keywords: mail4, nsbeta3
Whiteboard: [nsbeta3+] Partial fix in hand
Target Milestone: M18 → Future
massive reassign of account manager bugs -> sspitzer please feel free to put me back on the CC if you have any questions/comments
Assignee: alecf → sspitzer
Status: ASSIGNED → NEW
mass re-assign of account manager bugs to racham.
Assignee: sspitzer → racham
Mass assigning all racham's UI clean up bugs to me, with permission. Sorry for the spam.
Assignee: racham → hwaara
As far as I can see all bugs are fixed by now. Suggesting FIXED/WORKSFORME.
Marking Worksforme. jglick: It would be great if the Account Setup UI spec could be updated to reflect the order of entries in the POP Server panel that's in the product now. I'm sure there will be additional entries but for documentation purposes I'm listing what's present right now: - Server Type - Server Name - User Name - Port - Log onto this account at startup of Mail - Check for new messages every # minutes - Automatically download any new messages - Leave messages on server - Delete messages on server when they are deleted locally - Limit message download to # kB per message - Empty Trash on Exit - Local Directory
Worksforme.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Verified Worksforme. All three platforms checked.
Ninoschka, sorry for the delay. Account Settings spec is not updated and reflects your summary. http://www.mozilla.org/mailnews/specs/accounts/
Oops, NOW updated.
Jen, In the spec "Limit message download to # kB per message" appears after "Empty Trash on Exit". In the product it appears before "Empty Trash on Exit". Should the position be changed in the product or is it a mistake in the spec?
I don't think the order is real important as long as the items are there. Also, "Limit message download to # kB per message" could possibly be moved to an "Offline and Storage" panel per the Offline discussions.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.