5 ms·

I was expecting the easy path to display certificate view (removed in 56) to be returned in 59 [1], but apparently it will be in 60 behind a flag [2]. [1] http

I was expecting the easy path to display certificate view (removed in 56) to be returned in 59 [1], but apparently it will be in 60 behind a flag [2]. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=663971 https://bugs.chromium.org/p/chromium/issues/detail?id=663971 [2] https://textslashplain.com/2017/05/02/inspecting-certificates-in-chrome/ https://textslashplain.com/2017/05/02/inspecting-certificate...

codnee 9y ago
After 5+ years using Chrome, this single change made me move to Firefox.
- SXX 9y ago
  Hit similar problem and after go through bunch of trouble when I worked to update decade old website with non-UTF8 encoding and it's end up that Chrome removed that trivial encoding selection feature from menu. So I switched back to Firefox after probably 7 years with Chrome / Chromium and absolutely happy with it. Also end-up that modern web pretty much usable with NoScript and ability to install some YouTube enhancement addons is nice.
  - y4mi 9y ago
    You should try umatrix sometimes. It's made by the same person that created ublock origin and has a wonderful script blocking UX
tokenizerrr 9y ago
I still don't get why they did this. It's just a huge step back in every single way I can think of.
- aargh_aargh 9y ago
  For now, you can star the issue I linked to.
- UnoriginalGuy 9y ago
  It is so needless too. Users already had to click "Secure," and then a blue link, all they did was change a useful blue link (to the certificate info) to a useless one (Learn More[0]). As a technical user, I was using certificate info multiple times a day, even on sites where I didn't want nor need the developer bar open. Now I keep on opening the Developer Bar to check the certificate and it shoots me straight into emulation mode, disrupting my entire workflow. They should just re-add it at the bottom by "Site Settings." [0] https://support.google.com/chrome/answer/95617 https://support.google.com/chrome/answer/95617
- tmd83 9y ago
  That's what I was wondering. Whose brilliant idea was this and what was the rationale, does anyone know? There are quite a few decisions/bugs/lack-of-feature I see in google product that makes me wonder to whom such things make sense or doesn't matter.
j_s 9y ago
You can view the certs on the network tab of the developer tools without flipping any switches, right? I too wish this was part of the main address bar SSL status UI but was slightly relieved to find that it hadn't completely disappeared but rather been buried.
- iza 9y ago
  It's in the "Security" tab of the developer tools actually.
frik 9y ago
Wow. I thought it's a bug in my copy. I tried furiously clicking around and the popup had no cert-info. That's really bad! Bring the cert info feature back! Why should I trust HTTPS if one cannot even read basic cert info to begin with!? Even IE11 has it, as does FF.

codnee 9y ago

After 5+ years using Chrome, this single change made me move to Firefox.

SXX 9y ago
Hit similar problem and after go through bunch of trouble when I worked to update decade old website with non-UTF8 encoding and it's end up that Chrome removed that trivial encoding selection feature from menu. So I switched back to Firefox after probably 7 years with Chrome / Chromium and absolutely happy with it. Also end-up that modern web pretty much usable with NoScript and ability to install some YouTube enhancement addons is nice.
- y4mi 9y ago
  You should try umatrix sometimes. It's made by the same person that created ublock origin and has a wonderful script blocking UX

tokenizerrr 9y ago

I still don't get why they did this. It's just a huge step back in every single way I can think of.

aargh_aargh 9y ago
For now, you can star the issue I linked to.
UnoriginalGuy 9y ago
It is so needless too. Users already had to click "Secure," and then a blue link, all they did was change a useful blue link (to the certificate info) to a useless one (Learn More[0]). As a technical user, I was using certificate info multiple times a day, even on sites where I didn't want nor need the developer bar open. Now I keep on opening the Developer Bar to check the certificate and it shoots me straight into emulation mode, disrupting my entire workflow. They should just re-add it at the bottom by "Site Settings." [0] https://support.google.com/chrome/answer/95617 https://support.google.com/chrome/answer/95617
tmd83 9y ago
That's what I was wondering. Whose brilliant idea was this and what was the rationale, does anyone know? There are quite a few decisions/bugs/lack-of-feature I see in google product that makes me wonder to whom such things make sense or doesn't matter.

j_s 9y ago

You can view the certs on the network tab of the developer tools without flipping any switches, right? I too wish this was part of the main address bar SSL status UI but was slightly relieved to find that it hadn't completely disappeared but rather been buried.

iza 9y ago
It's in the "Security" tab of the developer tools actually.

frik 9y ago

Wow. I thought it's a bug in my copy. I tried furiously clicking around and the popup had no cert-info. That's really bad! Bring the cert info feature back! Why should I trust HTTPS if one cannot even read basic cert info to begin with!? Even IE11 has it, as does FF.