Closed (fixed)
Project:
Respond.js
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2011 at 20:39 UTC
Updated:
6 Dec 2011 at 19:58 UTC
Just wondering if you have plans to make the a full project and move it out of a sandbox?
Comments
Comment #1
ruplThis is a stub sandbox at the moment :(
For now I'd recommend Modernizr which can bundle respond.js
Comment #2
ruplThe sandbox now contains the basic functionality you need to get up and running. I'm going to implement Libraries support at the very least before tagging a release.
Comment #3
Michael Ware commentedI could not get this to module to work on IE. Eventually I realized/read that respond.js does not work with stylesheets pulled into a page using @import, which is how drupal pulls in stylesheet via the .info file. Instead, put the stylesheet that will use the media queries directly into your html.tpl.php file just after
print $styles;Hope that helps someone.
Comment #4
rupl@Michael Ware - That's correct. This script only works with
<link>and will not work with@import. However, Drupal 7 uses<link>tags for stylesheets when you enable CSS aggregation, so it starts working at that point. It's a good idea to enable this setting on all production websites anyway.Navigate to /admin/config/development/performance. Enable Aggregate and compress CSS files.
I have added a note to the project page, and will open a separate issue for some sort of administrative warning that reminds users that respond.js will not work until they enable CSS aggregation.
Comment #5
ruplIssue can be tracked here: #1350130: Issue an administrative warning when CSS aggregation is disabled
Comment #6
ruplRelease has been tagged, should be available on d.o momentarily!