Chrome is intending to change the behaviour of
<link rel="stylesheet">, which will be noticeable when it appears within
<body>. The impact and benefits of this aren't clear from the blink-dev post, so I wanted to go into detail here.
Previously when we've run into a contentious service worker design issue, we've asked web developers what they think. This has worked out pretty well in the past, with developer feedback directly informing spec changes. It's also great because we can blame y'all if you pick the wrong thing.
Well, it's that time again! Help us!
Yeah, ok, it's a touch bold to talk about something being the thing of the year as early as January, but the potential of the web streams API has gotten me all excited.
Streams can be used to do fun things like turn clouds to butts, transcode MPEG to GIF, but most importantly, they can be combined with service workers to become the fastest way to serve content.
I just had my responsive images epiphany and I'm writing it all down before I forget everything. This is what I know…
Recently, ppk claimed the web is going too fast in the wrong direction, and asked for a year's moratorium on web features. I was so angry I ran straight to a dictionary to find out what "moratorium" meant. Turns out it means "suspension".
I got a bit snarky about it on Twitter, which isn't really fair, so here's a more considered response:
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…