So desktop IE8 and below does not support media queries.
There is currently no version of IE Mobile that supports media queries.
If we build mobile first, then IE Mobile is pretty sorted. The trick part is how we degrade gracefully for desktop IE.
This is part of: #1077094: Make Bartik a responsive design - meta issue
Comments
Comment #1
Jeff Burnz commentedWell, there is no graceful degradation is there, really, lets all be honest about it - below IE9 there is no media query support, unless... we polyfill. In my mind if we are going to do mobile first, we have to polyfill.
Comment #2
lewisnymanNot true Jeff, we can use IE conditional comments to supply the current 960 layout. That is just one option we have.
Comment #3
Jeff Burnz commentedOK, yes we could use conditional comments, so what about other browsers or devices that do not support media queries, and how is this optimal for IE7/8 users - are we to choose many kb of CSS overrides in place of 1kb of js?
Comment #4
lewisnymanGood question. I'd like to point out that respond.js is no stallion. It doesn't support width queries set in ems. This is essential in my opinion.
If we do add a polyfill to core. We need to be careful what we choose and how we implement it.
It worth thinking about the best non JS solution for now, seeing as we are going to have to consider non MQ non JS browsers anyway.
It's actually possible for us to take advantage of IE's broken media parser to unconditionally load the css inside media queries it doesn't understand.
Comment #5
Jeff Burnz commentedWe're going to need a test bed to set up various approaches. Lets think about this:
1. A control that uses only media queries (our ideal solution).
2. Example that uses respond.js (ems are not a hard requirement, could just be a basic 320andUp example page).
3. ?
This doesn't need to be Bartik + Drupal but simply plain old HTML pages that we can load up in various browsers and see what is happening.
Comment #6
johnalbinWell, let's break this down…
If a mobile device doesn't support media queries than the only solution is to provide a mobile first responsive design. The default when a device doesn't know media queries or handle complex JavaScript or conditional comments is to provide a one-column responsive layout. Since the consensus I'm seeing for responsive designs is to be mobile first, I think we are on the same page. "mobile first" means we don't have to worry about the burden of mobile devices without media query support.
So then what about desktop devices? It turns out the only modern browser not supporting media queries is…IE!
Comment #7
lewisnymanI completely forgot to post it here but this issue pushed me to research and document the various methods of gracefully degrading media queries. It manifested itself as this article
Comment #8
dodorama commentedThis might help
#1465948: [meta] Drop some IE8 coddling from Drupal core
Comment #9
gmclelland commentedBe careful with conditional comments http://www.phpied.com/conditional-comments-block-downloads/ they block downloads in IE.
The conditional comments at the top of http://html5boilerplate.com/ templates are ok to use. You know the ones like:
Comment #10
Gaelan commentedRespond.js?
Comment #11
johnalbinI don't think we need a separate issue for this. It should be tackled along with #1192044: Convert Bartik's layout to mobile-first and responsive