Closed Bug 209082 Opened 21 years ago Closed 21 years ago

Certificate viewer is broken in Win32 build 2003-06-11-05-1.4

Categories

(Core Graveyard :: Security: UI, defect, P1)

1.0 Branch
x86
Windows 2000

Tracking

(Not tracked)

VERIFIED FIXED
psm2.4

People

(Reporter: junruh, Assigned: KaiE)

References

()

Details

(Keywords: fixed1.4, regression)

Attachments

(1 file)

1.) Visit a secure site such as https://www.verisign.com and click on the lock
icon, then on View.
What happens: The cert viewer does not show any info. Trunk build is OK.
To Kai for investigation.
Assignee: ssaux → kaie
I'm also seeing this on Linux 20030614.
This seems also be broken on current CVS Trunk builds.
My own 1.4 branch build based on 2003-06-03 behaved correctly.
A downloaded 1.4 branch build from 2003-06-12 is broken.

I'm updating my tree now.
Flags: blocking1.4?
Keywords: nsbeta1, regression
Priority: -- → P1
Target Milestone: --- → 2.4
I see the following new exception on the JS console after having pressed the
view button:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIX509CertDB.findCertByNickname]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://pippki/content/viewCertDetails.js :: setWindowName :: line 93"  data: no]
This bug was caused by the checkin from bug 208862.

It sees that unnamed windows no longer carry the name "_blank".

I guess the fix is to test for an empty string?
Attached patch Patch v1Splinter Review
Comment on attachment 125778 [details] [diff] [review]
Patch v1

Can you please review?
Attachment #125778 - Flags: superreview?(jst)
Attachment #125778 - Flags: review?(danm)
Comment on attachment 125778 [details] [diff] [review]
Patch v1

Sorry for busting your window. Your proposed change matches my change which
broke you, so that's all well and good. The overall effect will be slightly
different, though.

Currently, any window which was opened either with the name "" or "_blank" will
have a name of "". Previously, windows opened with "" would have been named "".
So your test for "" will catch another class of windows that it wasn't catching
before.

I'm guessing this won't be a problem for you. And glancing over
viewCertDetails.js, actually the new way seems like an improvement. So this is
probably all good, but I wanted to be sure you knew about the new gotcha.
Attachment #125778 - Flags: review?(danm) → review+
Thanks for the explanation. Yes, I think it is fine to execute the same code
block when having an empty window name, regardless whether that was explicitly
chosen or happens to be the default name.
Comment on attachment 125778 [details] [diff] [review]
Patch v1

sr=jst
Attachment #125778 - Flags: superreview?(jst) → superreview+
Comment on attachment 125778 [details] [diff] [review]
Patch v1

sr=jst
Fixed on trunk.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Attachment #125778 - Flags: approval1.4?
*** Bug 209775 has been marked as a duplicate of this bug. ***
Comment on attachment 125778 [details] [diff] [review]
Patch v1

a=asa (on behalf of drivers) for checkin to the 1.4 branch.
Attachment #125778 - Flags: approval1.4? → approval1.4+
a=adt to land this on the 1.4 branch by 2003-06-19 5am PST and no later please.
 Please mark this with the fixed1.4 keyword once this lands on the 1.4 branch. 
Thanks.
Fixed on the Mozilla 1.4 branch, after rc2.
Keywords: fixed1.4
*** Bug 209862 has been marked as a duplicate of this bug. ***
*** Bug 194714 has been marked as a duplicate of this bug. ***
*** Bug 209933 has been marked as a duplicate of this bug. ***
Verified.
Status: RESOLVED → VERIFIED
*** Bug 210364 has been marked as a duplicate of this bug. ***
*** Bug 210432 has been marked as a duplicate of this bug. ***
*** Bug 209709 has been marked as a duplicate of this bug. ***
*** Bug 210758 has been marked as a duplicate of this bug. ***
mozilla1.4 shipped. unsetting blocking1.4 request.
Flags: blocking1.4?
Product: PSM → Core
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: