smileyj68

9 ms·

1.
by smileyj68 13y ago
Definitely not supposed to, we're pushing a fix for that. Bit of a rush on the marketing site for launch...
2.
by smileyj68 13y ago
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.
3.
by smileyj68 13y ago
You don't like our Yeti? Aww. I won't tell him.
4.
by smileyj68 13y ago
We'll see if we can amp it up a bit.
5.
by smileyj68 13y ago
We tested pretty extensively, it looks okay...what device?
6.
by smileyj68 13y ago
Hmm, they should, have a light grey background. Maybe too light?
7.
by smileyj68 13y ago
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.
8.
by smileyj68 13y ago
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.
9.
by smileyj68 13y ago
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.
10.
by smileyj68 13y ago
Correct.
11.
by smileyj68 13y ago
Poor wording - we match the media queries and the last valid match is loaded, not each in sequence. We'll make that clearer.
12.
by smileyj68 13y ago
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
13.
by smileyj68 14y ago
Well said. If you need support for the top bar, shoot us an email, foundation@zurb.com. Happy to help.