So you want to trigger an event for a DOM element, without using jQuery? This blog post gives you a quick recipe for doing so.

The running example is about sending a submit event to a form. I needed to do that for a demo of user interface testing via CasperJS. And, unfortunately, the Form#submit method does not send that event on most web engines.

The main point of the blog post “Thoughts on asm.js vs PNaCl” (by Gregg Tavares) is:

It just seems like asm.js and PNaCl are closer than people are admitting.

Some of the other points he is making are more controversial, so be sure to read the comments to get the complete picture.

Infinity begins relatively early in JavaScript:

    > Math.pow(2, 1024)
    Infinity
    > Math.pow(2, 1023)
    8.98846567431158e+307

What is going on here?

[This post is part of a series on JavaScript quirks.]

Closures are a powerful JavaScript feature: If a function leaves the place where it was created, it still has access to all variables that existed at that place. This blog post explains how closures work and why one has to be careful w.r.t. inadvertent sharing of variables.

Web Components [1] are an upcoming standard for custom HTML5 user interface elements. Those UI elements will eventually become interchangeable between frameworks. Now the people behind AngularJS and Ember.js have described their plans for supporting Web Components.

Updates:

• [2013-07-16] Hello Polymer: Q&A with Google’s Polymer team [more information on Polymer]
• [2013-05-23] Plans for supporting Web Components in AngularJS and Ember.js

At Google I/O 2013, Google presented a new web user interface (UI) framework called Polymer. The way it works is indicative of the future of all web UI frameworks.

[This post is part of a series on JavaScript quirks.]

In most programming languages, variables only exist within the block in which they have been declared. In JavaScript, they exist in the complete (innermost) surrounding function:

    function func(x) {
        console.log(tmp); // undefined
        if (x < 0) {
            var tmp = 100 - x;  // (*)
            ...
        }
    }

Two tweets by Brendan Eich shed light on the history of JavaScript having both undefined and null [1].

Current technology encourages us to be continuously connected. This blog post predicts that that will change.