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.
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.