Closed
Bug 280413
Opened 20 years ago
Closed 16 years ago
Empty fields in account settings dialog after removing and re-adding a new email account.
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marco, Assigned: mscott)
Details
(Whiteboard: closeme 2008-08-28)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 After adding, removing an re-adding a new email account with exactly the same settings (without closing the account settings dialog in between) all fields of this accounts are empty or not checked/selected respectively. This seems to be only a dialog fields update issue, because if you close and reopen the account settings dialog the problem is gone i.e. the correct values are shown in the dialog fields. Reproducible: Always Steps to Reproduce: 1. Add a new email account in the account settings dialog 2. Remove the newly created email account (without closing the account settings dialog) 3. Add a new email account with the same settings as in step one (without closing the account settings dialog) Actual Results: All textfields/checkboxes of the new account are empty/not selected. (Workaround: After closing and re-opening the account settings dialog, the correct values are there.) Expected Results: The fields of the new account should contain the values as they do after closing and re-opening the account settings dialog.
| Reporter | ||
Comment 1•20 years ago
|
||
I forgot: I'm using the following version of Thunderbird: version 1.0 (20041206) [gentoo mail-client/mozilla-thunderbird-bin 1.0]
Version: unspecified → 1.0
Comment 2•20 years ago
|
||
i saw the same problem on thunderbird 1.0 but with WINDOWS 2000
Comment 3•20 years ago
|
||
I can reproduce this bug with 2005-03-21-05-trunk on Windows XP. please mark it --> CONFIRMED
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
| Reporter | ||
Comment 5•19 years ago
|
||
Reproduced today with Thunderbird 1.0.6 (20050716) on Linux. The bug is not severe and will not affect many people, but IMHO it is still a rather bad GUI behaviour.
Updated•18 years ago
|
QA Contact: account-manager
Comment 6•16 years ago
|
||
Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)
Whiteboard: closeme 2008-08-28
| Reporter | ||
Comment 7•16 years ago
|
||
This bug seems to be fixed in Thunderbird version 2.0.0.16 (20080724).
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 8•16 years ago
|
||
->WORKSFORME (FIXED is only used when known code changes resolved the issue) https://bugzilla.mozilla.org/page.cgi?id=fields.html#resolution
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•