Hacker News new | ask | show | jobs
by tscs37 3086 days ago
>it respects the standards

What about the time they broke passive event listeners for no other reason than "we say so"?

1 comments

Same for when they broke HTTPS support because "we say so". The proper solution of updating the RFC is too slow for them.
The passive listener case is, IMO, a bit more severe since when several web developers complained after having their websites broken, the chrome devs merely yelled "it's faster!" and there was that.

Chrome shouldn't be going around breaking webstandards without atleast consulting with other browser vendors, if Chrome breaks passive listeners and Firefox and Edge don't then that is an issue, period.