4 ms·
> Emily Stark writes: "Breaking changes happen often on the web, and as a developer it's good practice to test against early release channels of major browsers
by funOtter 5y ago
> Emily Stark writes: "Breaking changes happen often on the web, and as a developer it's good practice to test against early release channels of major browsers to learn about any compatibility issues upfront." ... First, she is flat out wrong – breaking changes happen very rarely on the web ... But second, and far more disturbing, is the notion that web developers should be continually testing their websites against early releases of major browsers. That's actually why there are web standards – so developers don't have to do ridiculous things like continually test their websites to make sure they're still working
Yes, so true. Concerning that a Google Chrome engineer does not know this.
- alisonkisk 5y agoA browser is a user agent. Web developers shouldn't expect browsers to support spam vectors like alert(). Browser extensions (ad blockers!) also "break" web pages. Should we wait for standards approval and web dev buy in?