As a user, I'm annoyed my browser will now be subject to a flawed implementation for however much longer it now takes to revert the reversion (de-facto standard or not). I most certainly can't be alone in this stance. While I empathize a subset of developers may have been caught off guard by changes, my empathy has limits: their inconvenience is not worth my browser safety. Why must users suffer at the hand of a few chest-thumping devs?
A little deference for history I think would also go a long way here: time and again Google has to kick the industry hard in it's complacency [2][3]. How quickly the industry seems to have forgotten that not all that long ago, developers [and administrators] had to be dragged kicking and screaming like toddlers, to support HTTPS adoption (and corresponding changes to the chrome UI). Was that change difficult then? You bet. Was it a net-good change in the long run? Hell yes.
As Bruce Wayne said to Alfred after laying waste to League of Shadow's headquarters in Nolan's Batman Begins:
"People need dramatic examples to shake them out of apathy [...]"
Chrome Security team, if you're reading this, keep on trucking.
- [1] https://bugs.chromium.org/p/chromium/issues/detail?id=106508...
- [2] https://bugs.chromium.org/p/chromium/issues/detail?id=106508...
- [3] https://security.googleblog.com/2018/02/a-secure-web-is-here...