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)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.4
People
(Reporter: junruh, Assigned: KaiE)
References
()
Details
(Keywords: fixed1.4, regression)
Attachments
(1 file)
796 bytes,
patch
|
danm.moz
:
review+
jst
:
superreview+
asa
:
approval1.4+
|
Details | Diff | Splinter Review |
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.
Comment 2•21 years ago
|
||
I'm also seeing this on Linux 20030614.
Comment 3•21 years ago
|
||
This seems also be broken on current CVS Trunk builds.
Assignee | ||
Comment 4•21 years ago
|
||
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.
Assignee | ||
Comment 5•21 years ago
|
||
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]
Assignee | ||
Comment 6•21 years ago
|
||
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?
Assignee | ||
Comment 7•21 years ago
|
||
Assignee | ||
Comment 8•21 years ago
|
||
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+
Assignee | ||
Comment 10•21 years ago
|
||
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 11•21 years ago
|
||
Comment on attachment 125778 [details] [diff] [review] Patch v1 sr=jst
Attachment #125778 -
Flags: superreview?(jst) → superreview+
Comment 12•21 years ago
|
||
Comment on attachment 125778 [details] [diff] [review] Patch v1 sr=jst
Assignee | ||
Comment 13•21 years ago
|
||
Fixed on trunk.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•21 years ago
|
Attachment #125778 -
Flags: approval1.4?
Comment 14•21 years ago
|
||
*** Bug 209775 has been marked as a duplicate of this bug. ***
Comment 15•21 years ago
|
||
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+
Comment 16•21 years ago
|
||
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.
Assignee | ||
Comment 18•21 years ago
|
||
*** Bug 209862 has been marked as a duplicate of this bug. ***
Comment 19•21 years ago
|
||
*** Bug 194714 has been marked as a duplicate of this bug. ***
Comment 20•21 years ago
|
||
*** Bug 209933 has been marked as a duplicate of this bug. ***
Comment 22•21 years ago
|
||
*** Bug 210364 has been marked as a duplicate of this bug. ***
Comment 23•21 years ago
|
||
*** Bug 210432 has been marked as a duplicate of this bug. ***
Comment 24•21 years ago
|
||
*** Bug 209709 has been marked as a duplicate of this bug. ***
Comment 25•21 years ago
|
||
*** Bug 210758 has been marked as a duplicate of this bug. ***
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
•