Closed Bug 75615 Opened 24 years ago Closed 23 years ago

[meta] Cannot get new site certificates when using PSM2 and a high-res screen

Categories

(Core Graveyard :: Tracking, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: chofmann)

References

()

Details

(Keywords: meta)

Attachments

(1 file)

Currently it is impossible to get new certificates when using PSM2. The dialog that comes up is too small for its content on a high-res screen (bug 75596), and being modal it cannot be properly resized due to bug 75610. Combined with bug 75595, which prevents one from using Escape or Enter to close the dialog, this means that the application is effectively stalled.
adding dependencies. Adding keywords (getting a new certificate is a security smoketest)
Depends on: 75595, 75596, 75610
Keywords: meta, smoketest
Arent's smoketests for default builds? (According to komodo, psm2 still hasn't landed)
Marking down to critical. PSM2 has not landed on the trunk, so how can this be a blocker?
Severity: blocker → critical
R.K.Aa, you're right. Removing smoketest keyword but keeping blocker severity as advised by Asa. As soon as the PSM2 branch lands this will become a smoketest blocker.
Severity: critical → blocker
Keywords: smoketest
sending to PSM so the right people will be looking at it.
Assignee: ben → ddrinan
Component: XP Apps: GUI Features → Client Library
Product: Browser → PSM
QA Contact: sairuh → junruh
Version: other → 2.0
Marking dupe of bug 75596. Even if you could get past that dialog, a public key is not presently being generated - see bug 75608. *** This bug has been marked as a duplicate of 75596 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Are we talking about the same functionality? I am talking about a site that has a site certificate. When I go to that site, I am prompted to install the new site certificate. This works just peachy for me with PSM2 and lower resolutions.... Reopening.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: [meta] Cannot get new certificates when using PSM2 and a high-res screen → [meta] Cannot get new site certificates when using PSM2 and a high-res screen
Target Milestone: --- → 2.0
Getting this on Linux with 2001050305-M0.9 and 2001050309-trunk. Makes PSM unusable for sites that do not have a certificate authorized by a CA known to the browser. In my case I am using 100dpi fonts, with the X server and Mozilla DPI set to 96. May I suggest as a quick fix possibly for 0.9 at least making the dialog window resizable?
I doubt making it resizable is a "quick fix". One can resize it fine; it just doesn't repaint. This is likely a problem somewhere in the event handling....
As shown in the image I'll attach, this doesn't appear to be a Windows Issue any longer. Using 2001050317-Win2k, 1280x1024, 96 dpi, the window shows fine..
Keywords: donttest
Please try with various font setups on Windows (including large fonts). This seems to be a font-related issue, partially.
There's much discussion (& Screenshots) of this very issue in bug 75596.
Boris: You're right, I tried forcing my window manager to make the dialog window resizable and it doesn't repaint. (Using build 2001050708-trunk) Maybe since the dialog thinks it's modal it refuses to accept resize events?
*** This bug has been marked as a duplicate of 75610 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
fix the dialog.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
bug 79843 duplicates this bug.
*** This bug has been marked as a duplicate of 75596 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
Er, no. This is a tracking bug for the problem. Dupping it against a bug it tracks seems like a strange idea. Reopening.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
over to tracking to stop it from being resolved dup all the time.
Assignee: ddrinan → chofmann
Status: REOPENED → NEW
Component: Client Library → Tracking
Product: PSM → Browser
QA Contact: junruh → chofmann
Target Milestone: 2.0 → ---
Version: 2.0 → other
Shouldn't it be marked as fixed as all the tracked bugs are resolved now?
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: