234325 - "Manage CRLs" window do not update "Last Update" and "Next Update" after CRL update

Status: RESOLVED EXPIRED

(Core Graveyard :: Security: UI, defect)

Description

[Oleg Titov]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113

"Manage CRLs" window do not update "Last Update" and "Next Update" after CRL
update, this values get updated only af\ter close window-open window procedure

Reproducible: Always
Steps to Reproduce:
1. Open Edit, Preferences, Privacy & Security, Validation
2. Select "Manage CRLs"
3. Select any CRL in the list
4. Take a note of "Last Update" and "Next Update"
5. "Update"
6. Mentione values have not changed
7. Close "Manage CRLs" window
8. Open "Manage CRLs" window - values updated



related to bug #150589

Comment 1

[Gervase Markham [:gerv]]

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 2

[Gervase Markham [:gerv]]

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.

Comment 3

[Nico R.]

I can reproduce this bug for Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/6.0. Can someone with appropriate privileges please reopen this bug? Or should I file a new bug against Firefox?

This could be related to bug 104137.

Comment 4

[Daniel Coloma:dcoloma]

Why this should be a blocker?