gonchuki

3 ms·

1. 1.▲
   by gonchuki 15y ago

   add to that list that the Chrome dev tools don't display errors in red in the network tab. A 200 next to a 404 is nearly to impossible to distinguish at first sight (basically, if you are looking at the name of the file, you are not looki
2. 2.▲
   by gonchuki 15y ago

   Chrome updates also result in JavaScript breakage. File/Blob API is an example that, while being experimental and a moving target, happened on the background and broke from one launch of the browser to the other without the dev knowing what
3. 3.▲
   by gonchuki 15y ago

   Function.prototype.apply.apply(console.log, [console, arguments]); Works both on IE9 broken console.log, and regular console.log from other vendors. Same hack as using Array.prototype.slice to convert arguments into a real array.