add "unfinished" state to accounts

VERIFIED FIXED in M14

Status

P3
normal
VERIFIED FIXED
19 years ago
14 years ago

People

(Reporter: bugzilla, Assigned: alecf)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
If you get a JS crash in the "Account Settings" and the fields of the current
account are blank because of this crash and you press OK, empty fields are
written to the prefs.js
I dont think I should be possible to write empty fields to the prefs.js file.
At least not for:
- Account Name
- Email address

The other fields may be left blank!
(Assignee)

Updated

19 years ago
Blocks: 23411
(Assignee)

Updated

19 years ago
No longer blocks: 23411
Status: NEW → ASSIGNED
Target Milestone: M14
(Assignee)

Updated

19 years ago
Blocks: 23411
(Assignee)

Updated

19 years ago
Summary: It shouldn't be possible to write empty Account setting to the prefs.js → add "unfinished" state to accounts
(Assignee)

Comment 1

19 years ago
updating bug to reflect the actual work that must be done.

Updated

19 years ago
QA Contact: lchiang → nbaca

Comment 2

19 years ago
I'd push this out if 23411 didn't depend on it....
(Assignee)

Comment 3

19 years ago
This work is actually done now... 
(Assignee)

Comment 4

19 years ago
oops, mark it fixed
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 5

19 years ago
Build 2000-03-06-10M15: NT4
Build 2000-03-06-13M15: Linux 6.0

Alec, after creating a variety of accounts I looked for a pref entry
("mail.server.server#.valid", true); statement and it was never created.
In some other tests I was able to get Account Wizard to crash. After checking 
the prefs file, it did not write any new entries to the pref file, which is 
good.

Why am I not seeing the "valid" statements that you mentioned? Since the crash 
does not result in writing erroneous information to the pref file, can I mark 
this Verified?
(Assignee)

Comment 6

19 years ago
Eh, I guess the valid stuff doesn't really matter that much. the bit about
getting the Account Wizard itself to crash should never happen! we should file
any new bugs about that, with stack traces...

The account wizard should prevent _this_ bug from ever happening by requiring
users to enter stuff in every field... I guess was I meant was that you could
try creating an account as normal (with the expectation that the wizard doesn't
crash!) and then go into the account manager, and clear out some fields like
email and account name, then try using the account.... 

Comment 7

19 years ago
Build 2000-03-07-08M15: NT4, Linux 6.0, Mac 8.5.1
Verified Fixed. The following operations were performed without a crash. 
Also, pop-up messages appeared directing how to resolve the problem if no entry 
existed.

- The Account Wizard requires entries for each text box and no longer crashes. 
The crash mentioned in this bug was logged and is now fixed.
- In Account Settings I deleted the Username and Email entries. Then created a 
new message and at Send time it displayed a message stating to go back to prefs 
to enter an email address. I went back and entered a valid email address and 
then was able to send a new message. 
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.