New issue
Advanced search Search tips

Issue 666888 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Feature



Sign in to add a comment

Certificate viewer UI is unnecessarily small and cumbersome to use.

Reported by jonat...@haitu-yu.com, Nov 18 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36

Steps to reproduce the problem:
1. Open the certificate viewer from the security panel
1. Click the "Details" tab

What is the expected behavior?

What went wrong?
There are at least two issues relating to the fixed maximum size of the certificate viewer.

Firstly, the certificate hierarchy section can only accommodate 2 full lines. Commercial CAs do not sign end-entity certificates with their root certificates, meaning there will practically always be at least 3 entries. Users are therefore forced to scroll to see the entire certificate chain. In addition, when there are 2 or more intermediate CAs in the chain, it is not evident how long the chain is without scrolling, nor is it possible to know what depth a given certificate is in the chain without counting them as one scrolls or guessing based on the amount of whitespace the entry is indented by.

Secondly, the text box that displays the data for the currently selected field (#cert-field-value), can only accommodate a maximum of 5 lines. For most purposes this is OK, however, some fields can be require significantly more than this. For example, the Subject Alternative Name field does not have an defined upper bound on the number of entries that may be present. Services like Cloudflare routinely issue certificates with large numbers of SANs.

These issues could be resolved by allowing the certificate viewer to expand to the full height of the window, instead of arbitrarily limiting its maximum height. In addition, the certificates in the chain should probably be numbered so the depth of a given certificate does not need to be counted by hand or guessed.

Did this work before? N/A 

Chrome version: 54.0.2840.100  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 23.0 r0
 
chrome-cert-viewer.png
105 KB View Download
Cc: ligim...@chromium.org
Components: -UI Security UI>Browser>Interstitials
Labels: -Type-Bug M-56 Type-Feature
Tagging as a Feature Request.
Does this request also apply on CHhome OS?
Status: Untriaged (was: Unconfirmed)
Since this is a feature request marking it as untriaged.

Thanks.
Status: Available (was: Untriaged)
I think Available is more appropriate.
Labels: -M-56 -Via-Wizard-UI
Status: Untriaged (was: Available)
Lucas: Isn't it fair to say it's confirmed, but hasn't been reviewed for priority or assignment? Also removing the Milestone, since it needs to get some UI love.
Components: -Security -UI>Browser>Interstitials
Labels: -Pri-2 Team-Security-UX Pri-3
Ah, yes, I didn't notice the milestone; thanks for removing.
Priority is definitely low from the Enamel side, though. (Does anyone else maintain this surface?)
Components: Platform>DevTools>Security
What's the operating system? Isn't this dialog native?
Components: -Platform>DevTools>Security
This bug is for Linux. The dialogue is indeed native.
Components: Internals>Network>Certificate
certificate_viewer_webui.cc

void CertificateViewerModalDialog::GetDialogSize(gfx::Size* size) const {
  const int kDefaultWidth = 544;
  const int kDefaultHeight = 628;
  size->SetSize(kDefaultWidth, kDefaultHeight);
}

We could easily bump up the default height if we wanted, but dynamically-sizing the height could prove to be a bug farm.
Cc: elawrence@chromium.org
Components: Platform>DevTools>Security
Status: Available (was: Untriaged)
Labels: Hotlist-CertificateViewer
Components: UI>Browser>CertificateViewer
Labels: -Hotlist-CertificateViewer
Labels: Hotlist-EnamelAndFriendsFixIt
Components: -Platform>DevTools>Security
Labels: -Hotlist-EnamelAndFriendsFixIt
Status: Archived (was: Available)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment