3 ms·

Wouldn't that have been the case everywhere before JS browser support standardized to ES 2015 and above?

• int_19h 3y ago
  It's a question of presentation. Back then (and to be clear, I'm talking about 00s here) the correct way was to point out that something might not even be doable in cross-browser way at all, and listing the proprietary features that'd let you do it in specific browsers while clearly labeling them as proprietary. Quality websites would do that, while w3schools and the likes would just give you the snippet for (usually) IE. Worse yet, in many cases they would keep suggesting the old proprietary approach even after a new standardized way of implementing something showed up.