2 min read

Chrome out of control breaking the web

Chrome out of control breaking the web

Standards, who needs them?
Google Chrome certainly doesn't..

It is blatently obvious Google's disdain of w3c, web developers, and just simple web users expecting sites they visist to continue to work while they upgrade browsers to stay secure.

Yes, disdane, Google proves their superiority complex knows no bound when they call breaking the web an intervention like its justified, basically we all want it but not realise.

Back in July 2016 I wrote about a new feature called "Passive Event Listeners" that were an optional opt-in nice new feature to speed up your web pages but it was woefully immature riddled with implementation problems and gotcha's.

A year later and without fixing any of the usability or breaking changes, Google see's fit to make the feature on by default.
I know what you're thinking, no big deal right? Wrong, it's a huge deal, check this out.
To have a working web page that uses browser events (a core feature all sites use) We now need to;

  • Feature Detect a new native browser feature detection can be used
  • (no) Use a side-effect method of feature detection for browser events
  • If passive event is on, addEventListener 3rd argument is a dictionary
  • (no) passive events not available addEventListener 3rd argument is a flag for capture
  • Feature detection for defaultPrevented (try steps 1 and 2 above)
  • (no) freely use e.preventDefault() as we have for decades
  • (yes) e.preventDefault() is ignored when defaultPrevented is available, this is Chrome's intervention mode with forced use of passive event listeners enabled

Take that web developers!

Now what about other browsers like Firefox, IE, Edge, Safari, Mobile versions of each?

Now what about transpilers? You like TypeScript, CoffeeScript, React, Dart, [insert other transpiled to JavaScript source code here] right? Can you even support Chrome any more?

Transpilers alone give JavaScript the reputation of being more complex and high entry barrier then even Assembly or C. That's just transpilers alone that makes the entry barrier so high.. No one writes Prototypal JavaScript anymore, but if they did Browser vendors are now making the JavaScript ecosystem even more complex even for the lowest entry barrier then the most complex languages there is, not easier!

Is it a good time to abandon web development altogether?