smileyj68

Definitely not supposed to, we're pushing a fix for that. Bit of a rush on the marketing site for launch...

There were some definite compatibility issues we ran into and while jQuery 2 isn't perfect, it's pretty good, good enough we felt confident switching back from Zepto. Nothing against Zepto, just pragmatism.

You don't like our Yeti? Aww. I won't tell him.

We'll see if we can amp it up a bit.

We tested pretty extensively, it looks okay...what device?

Hmm, they should, have a light grey background. Maybe too light?

Lamentably, yes. I'd suspect the prefixes will drop off this year but we're sort of stuck with the browser adoption in this case.

There's a media query available (with prefixes, right now) for pixel density – a retina MBP reports it as 2 whereas a standard one reports it as 1. So you can have a media query for a pixel density >= 2, etc.

From what I've heard srcset is the likely eventual standard (as oppose to the picture element) but the timeline there is...long and murky.

Correct.

Poor wording - we match the media queries and the last valid match is loaded, not each in sequence. We'll make that clearer.

Checking network speed is actually a great idea - we'll investigate this. The reason we use the img src (which as you noted means you might load two images) is twofold: so that if your image is the same aspect ratio, you'll get an immediate load of something before the better image comes in (without which you'll have a really nasty reflow). This also guarantees you'll get something that works if JS is disabled or unavailable.

Please submit pull requests or issues for ways we can make this better, we're all ears.

Well said.

If you need support for the top bar, shoot us an email, [email protected]. Happy to help.