Closed
Bug 438692
Opened 17 years ago
Closed 17 years ago
Bad certificate and similar messages when browser.xul.error_pages.enabled is false are inconvenient
Categories
(Core Graveyard :: Security: UI, defect)
Core Graveyard
Security: UI
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 439062
M1
People
(Reporter: glandium, Assigned: KaiE)
Details
When disabling "xul error pages", docshell pops-up alerts about the certificate problem. The first problem is that is doesn't allow to ignore the error, but I won't argue a lot about that. The second problem is that the strings displayed don't have html tags stripped out, so you end up with messages such as:
The certificate is only valid for <a id="cert_domain_link" title="*.mozilla.org">*.mozilla.org</a>, which is not really nice.
A side effect of the first problem (though it might not be the same code path) is that embedding applications are *forced* to use the "Firefox-way" of handling certificates errors while they may want their own UI to handle that (or hack around neterror, but that would exclude some kinds of UIs).
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
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
•