UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Goto a TLS web side
2. Try to get the certificate to see, why chrome is not satisfied with the X.509 certificate
3. Now you must enable the developer console to get the information

What is the expected behavior?
That if I click on the red TLS icon, I can directly open a X.509 certitcate viewer.
So end users will have not to hasssle with the developer mode.

What went wrong?
I do not know, why this feature was removed in a past version, but it was a stupid idea.
If something is wrong with the certificate in a TLS handshake, then it should be easy to get the information about that.

Do not make the support temas crazy with this.

Did this work before? N/A 

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.12.4
Flash Version: