Closed Bug 415786 Opened 16 years ago Closed 16 years ago

escrow warning dialog is broken

Categories

(Core :: Security: PSM, defect, P2)

defect

Tracking

()

VERIFIED FIXED
mozilla1.9beta4

People

(Reporter: KaiE, Assigned: KaiE)

References

Details

(Keywords: late-l10n, regression)

Attachments

(2 files, 1 obsolete file)

Try to open chrome://pippki/content/escrowWarn.xul
(This dialog will be shown during some crypto operations, such as certificate enrollment.)

The dialog fails to open with an error message, because one of the strings is no longer available.

The string 
  <!ENTITY examineCert.label "View Certificate">
got accidentially removed from pippki.dtd as part of the changes for bug 327181.
Attached patch Patch v1 (obsolete) — Splinter Review
Depends on: https-error-pages
Attachment #301513 - Flags: ui-review?(beltzner)
Attachment #301513 - Flags: review?(rrelyea)
Keywords: late-l10n
Comment on attachment 301513 [details] [diff] [review]
Patch v1

This doesn't need ui-review.
Attachment #301513 - Flags: ui-review?(beltzner)
Bug 327181 removed the following comment, too:

<!-- Strings for the MismatchDomain dialog  -->

Not sure if that comment still applies, or should be replaced with something more reasonable in the new patched world.
(In reply to comment #3)
> Bug 327181 removed the following comment, too:
> <!-- Strings for the MismatchDomain dialog  -->

That dialog got completely removed, and my intention was to remove the associated strings.

I had missed the cert examineCert.label was still used somewhere else.
But on the other hand I didn't remove the accesskey, which makes me believe I simply deleted that line without thinking enough...

If you think it helps, I could add a comment that lists the name of the dialog where this string is being used (escrowWarn).
I think we should move both entities down to the escrow entities, then.

I guess that'd be more useful than adding a comment in this case.
Attached patch Patch v2Splinter Review
This addresses Axel's proposal and moves both strings further down.
Attachment #301513 - Attachment is obsolete: true
Attachment #301523 - Flags: review?(rrelyea)
Attachment #301513 - Flags: review?(rrelyea)
Comment on attachment 301523 [details] [diff] [review]
Patch v2

r+ yes, let's get this fixed.

bob
Attachment #301523 - Flags: review?(rrelyea) → review+
Flags: blocking1.9?
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Comment on attachment 301523 [details] [diff] [review]
Patch v2

Need explicit approval for this since it's late-l10n.
Attachment #301523 - Flags: approval1.9?
Comment on attachment 301523 [details] [diff] [review]
Patch v2

This patch has a "yes, please approve" from me.
Attachment #301523 - Flags: approval1.9? → approval1.9+
fixed

Checking in en-US/chrome/pippki/pippki.dtd;
/cvsroot/mozilla/security/manager/locales/en-US/chrome/pippki/pippki.dtd,v  <--  pippki.dtd
new revision: 1.5; previous revision: 1.4
done
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
FYI, the check in was too late for today's nightly builds, but builds dated on or after 2008-02-08 should be fixed.
(In reply to comment #12)
> FYI, the check in was too late for today's nightly builds, but builds dated on
> or after 2008-02-08 should be fixed.

Actually, we respun nightlies, so it did make it in today. :)
verified fixed using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008050804 Minefield/3.0pre and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050614 Minefield/3.0pre and the steps to reproduce from kai.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: