Closed
Bug 217214
Opened 21 years ago
Closed 19 years ago
certificate manager is filled (added) with lot of empty fields when i delete a certificate
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: pelikan, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030718 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030718 snapshot to this bug on the page http://pelikan.host.sk/mozilla When i delete a certificate from the certificate manager (preferences->security) the box is filled (added) with lot of empty fields... I think the number of empty fields is equal to number of fields before deleting. When i will now delete a next certificate, new empty fields are added... Close and re-open the manager and all it's OK Reproducible: Always Steps to Reproduce: 1.open certificate manager & delete some certificate 2. 3. Actual Results: the box is filled (added) with lot of empty fields...
Comment 1•21 years ago
|
||
I get a 403 (forbidden) error on http://pelikan.host.sk/mozilla.
Comment 2•21 years ago
|
||
you can try http://pelikan.host.sk/mozilla/
Reporter | ||
Updated•21 years ago
|
Updated•21 years ago
|
Comment 3•21 years ago
|
||
-> PSM
Assignee: bugs → ssaux
Component: Preferences → Client Library
Product: Browser → PSM
QA Contact: sairuh → bmartin
Version: Trunk → unspecified
Comment 4•20 years ago
|
||
Works for me Mozilla 1.6 MacOS 10.3 (Modulo the fact that one shouldn't be able to delete these in the first place--they come back the next time you pull up the cert manager.)
Comment 6•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/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•