With the recent Preferences scramble I had to re-find the Certificate Manager in order to manipulate my client certificates. There's no Advanced anymore, OK... Is there any page that looks like it contains the stuff that used to be under Advanced... nah. Something something network? Nah. Well, guess I've got to scan each and every section to see if I can find it. I had to do several skimming passes until I finally found it, nestled in what I believe to be a somewhat erroneous location. The "View Certificates..." button is under Privacy & Security, sure, that's fine. Didn't think of looking there first, as the old top-level security thing didn't have them. However, it's aligned to the right of "[X] Query OCSP responder servers to confirm the current validity of certificates" as if it was something OCSP-specific. Pretty much everywhere else the buttons on the right hand side match what's on their left, this is a jarring occurrence of where it's not. Thanks for this reorganization - it's always fun to update end-user documentation with screenshots across systems so that non-technical users can manipulate their client certificates. Please note that this is functionality that actual mortals use to get their science done, not just something niche for sysadmins and other network people. A large part of the scientific community are dealing with client certificates for storage, job submission, and website authentication - it'd be nice if we'd have something that doesn't make them even more negative against certificates. We're going to have a lot of support load from end users as they're renewing and exporting their certificates, as Firefox is our recommended method of acquiring client certificates since Chrome removed <keygen>.

Requesting needinfo from Tina who worked on the UX for this. Tina, what do you think?

Adding Cindy in case she can get to this before Tina.

I think this is a duplicate of Bug 1172499.

I don't think #1172499 is the same. That is about un-exposing/removing the OCSP preferences. It may incidentally resolve this bug, but this bug is a fundamentally different issue about incorrect UX for the right-aligned items, not the left-aligned (OCSP) items.