I'd argue that Chrome is the new IE by a long stretch:
Has an almost monopolistic position, and even other browsers (Opera, Edge, etc) have switched to the Chromium engine because it's more cost effective than chasing Chromes new CSS features that aren't spec.
Implement their own features that aren't in the spec. Most of the -webkit- prefixes in CSS are their fault, and is developers use them for core behaviour rather than progressive enhancement, meaning a lot of websites don't work well on other browsers (Fx & Safari)
They're removing features that have been part of the web for decades (alert(), confirm(), & prompt() in cross-origin iframes) which cause huge functional and accessibility problems.
So much of this reminds me of some of the very same things that Microsoft was doing in the early IE era (4 - 5.5).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd argue that Chrome is the new IE by a long stretch:
-webkit-prefixes in CSS are their fault, and is developers use them for core behaviour rather than progressive enhancement, meaning a lot of websites don't work well on other browsers (Fx & Safari)alert(),confirm(), &prompt()in cross-origin iframes) which cause huge functional and accessibility problems.So much of this reminds me of some of the very same things that Microsoft was doing in the early IE era (4 - 5.5).