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

For now, you can star the issue I linked to.

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.

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

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.

You should try umatrix sometimes. It's made by the same person that created ublock origin and has a wonderful script blocking UX

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.

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.

It's in the "Security" tab of the developer tools actually.