But also partly because of comments along the lines of 'Google is pushing the EV changes into the spec'. I will admit to some amusement in watching all this play out, partly because the ludicrous claims about EV efficacy really come crashing down when it's no longer visible to the end user.

With both browsers auto-updating for most people, we're about 10 weeks out from no more EV and the vast majority of web users no longer seeing something they didn't even know was there to begin with! Oh sure, you can still drill down into the certificate and see the entity name, but who's really going to do that? You and I, perhaps, but we're not exactly in the meat of the browser demographics. Starting in Version 77, Chrome will move this UI to Page Info, which is accessed by clicking the lock icon.ДЄnd here's the Firefox announcement: In desktop Firefox 70, we intend to remove Extended Validation (EV) indicators from the identity block (the left hand side of the URL bar which is used to display security / privacy information).Д¬hrome 77 is currently scheduled to ship on September 10 and Firefox 70 on October 22. Here's the Google announcement: On HTTPS websites using EV certificates, Chrome currently displays an EV badge to the left of the URL bar. The writing might have been on the wall a year ago, but the death warrant is now well and truly inked with both Chrome and Firefox killing it stone cold dead. The only proponents of EV seemed to be those selling it or those who didn't understand how reliance on the absence of a positive visual indicator was simply never a good idea in the first place. The entity name had just been removed from Safari on iOS, it was about to be removed from Safari on Mojave and there were indications that Chrome would remove it from the desktop in the future (they already weren't displaying it on mobile clients).

Almost one year ago now, I declared extended validation certificates dead.

Safari vs firefox 2019 journal articles