Turns out, mouse events don't fire when the pointer is over disabled form elements, except in Firefox. This is annoying when implementing things like drag & drop.

A few weeks ago I was at Heathrow airport getting a bit of work done before a flight, and I noticed something odd about the performance of GitHub: It was quicker to open links in a new window than simply click them. Turns out it was a lack of streaming…

I played with the web audio API for the first time recently, so I thought I'd write up what I learned. I think that's my job or something.

One of the great things about SVG is you can use media queries to add responsiveness to images, but which viewport triggers those media queries?

On July 28th-29th we met up in the Mozilla offices in Toronto to discuss the core service worker spec. here are the headlines…

rel="noopener" prevents opened pages tampering with the original page, but it also has a performance benefit.

Getting caching right yields huge performance benefits, saves bandwidth, and reduces server costs, but many sites half-arse their caching, creating race conditions resulting in interdependent resources getting out of sync.

Template literals are pretty cool right?

const areThey = 'Yes';
console.log(`${areThey}, they are`); 
// Logs: Yes, they are

But what if they could produce a stream?

The pattern in the previous post covers the 90% case of multi-stage CSS loading, and it's really simple to understand. But, would you like to hear about a pattern that covers ~100% and is absurdly complicated? Well, take my hand, and follow me into the next paragraph…