ServiceWorker brief overview gives you control over caching and how requests are handled. It doesn't give you patterns, you create them yourself. Let's look at a few!

ES6 gives us a new way to iterate, and it's already supported in stable releases of Firefox, Chrome, & Opera. Here it is…

With ServiceWorkers you can control requests to any page on your origin, and any of the subresource requests made by those pages. This is powerful stuff, and I'm curious to know what security measure you think is appropriate…

The implementation for ServiceWorker has been landing in Chrome Canary over the past few months, and there's now enough of it to do some cool shit!

Optimising fonts is pretty difficult for larger sites. There's an easy solution, although only some browsers support it.

There's a bit of disagreement over the behaviour of requests and responses in the fetch API, curious to know what you think…

The first draft of the service worker spec was published today! It's been a collaborative effort between Google, Samsung, Mozilla and others, and implementations for Chrome and Firefox are being actively developed. Anyone interesting in the web competing with native apps should be excited by this.

iOS has hidden the pathname of URLs for some time now, but recently Chrome Canary introduced something similar behind a flag.

I'm not involved in the development of Chrome experiment at all, but I've got more than 140 characters worth of opinion on it…

If you set an element to display: none the browser ignores all of its children, if a child sets itself to display: block it will remain hidden. This isn't true of visibility.