I’ve been offline today, but thanks so very much for the great feedback—I really appreciate the thoughtful discussion.
camerondaigle, that’s a casualty of using TextMate to parse calculations with Google Calculator. I used to use Calculator.app, but started relying on TM because it’s so easy to use.
deanoj, I haven’t seen the IE issue you mentioned. My experience has been that @@media@ blocks are ignored by IE, but the rest of the CSS is still parsed successfully. But I’d have to investigate that further.
Tim Wright, thanks very much for your feedback. And I completely agree: as we saw with media types, the market can quickly outpace the spec, and our detection methods may (or may not) play out. Time will tell. But I’m optimistic that media queries are right for, well, right now.
Scott, you grabbed the very resource I was going to respond with. PPK(Peter-Paul Koch) and lukew are two of the people I’ve learned the most from on that intermediary resolution layer.
Dave Warfel, thank you for catching that typo! I’ll investigate. As for your syntax question, I don’t have any real insight. Though I believe the sample code you pasted in though would divorce the media type (
media screen) from the query (min-width: 1300px) that follows it. Does that help at all?
Toby and Sean, great question. I’m no performance guru, but divvying up your
@media queries into separate
link elements would just cost additional HTTP requests. But I’d defer to the experts on that one. In either event, you’d want to pair the approach to your site’s needs.