Robert Nyman is a web developer who has written about JavaScript, CSS, browsers, and HTML5 forms.
HN commenters link him for JavaScript semicolon insertion pitfalls, CSS pointer-events click-through, HTML5 input types, and jQuery-era trivia.
jQuery in ~2008 was when it kinda took off, but jQuery was itself an outgrowth of work done before it on browser compatibility with JavaScript. In particular, events.
Internet Explorer didn’t support DOM events, so addEventListener wasn’t cross-browser compatible. A lot of people put work in to come up with an addEvent that worked consistently cross-browser.
The DOMContentLoaded event didn’t exist, only the load event. The load event wasn’t really suitable for setting up things like event handlers because it would wait until all external resources like images had been loaded too, which was a significant delay during which time the user could be interacting with the page. Getting JavaScript to run consistently after the DOM was available, but without waiting for images was a bit tricky.
These kinds of things were iterated on in a series of blog posts from several different web developers. One blogger would publish one solution, people would find shortcomings with it, then another blogger would publish a version that fixed some things, and so on.
This is an example of the kind of thing that was happening, and you’ll note that it refers to work on this going back to 2001:
https://robertnyman.com/2006/08/30/event-handling-in-javascript-an-alternative-addevent-solution/
When jQuery came along, it was really trying to achieve two things: firstly, incorporating things like this to help browser compatibility; and second, to provide a “fluent” API where you could chain API…
Just casual trivia:
One of the contemporaneous competitors to jQuery was called "DOMAss".
https://robertnyman.com/2007/03/02/domass-renamed-to-domassistant-with-added-prototypejquery-compatibility/
You'll get better performance with
for (var i=0, l=myLinkCollection.length; i<l; i++) { }
http://robertnyman.com/2008/04/11/javascript-loop-performance/
The click-jacking ability has been known for over a year now: http://robertnyman.com/2010/03/22/css-pointer-events-to-allow-clicks-on-underlying-elements/
Actually BSD style causes problems in Javascript due to semicolon insertion.
http://robertnyman.com/2008/10/16/beware-of-javascript-semicolon-insertion/
You are right to expect this from Microsoft, they've done it before:
http://robertnyman.com/2009/01/26/microsoft-force-installs-firefox-extension/