3 ms·
Same for when they broke HTTPS support because "we say so". The proper solution of updating the RFC is too slow for them.
by rkeene2 9y ago
Same for when they broke HTTPS support because "we say so". The proper solution of updating the RFC is too slow for them.
- tscs37 9y agoThe 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.