Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I noticed this on OpenChurch, I am going to have to disable the responsive layout I have for mobile because of it. Basically the 'mobile' layout is what is getting rendered for ie. I would request some way to disable for ie altogether. For instance my OC theme is only using the mobile layout and so I don't really care to load any of the responsive media queries for ie at all.
Comment | File | Size | Author |
---|---|---|---|
#12 | responsive_js_breaks_with_page_caching-1541752-12.patch | 3.18 KB | nielsonm |
Screen Shot 2012-04-21 at 9.01.26 AM.png | 607.59 KB | drupalninja99 |
Comments
Comment #1
sheena_d CreditAttribution: sheena_d commentedI'm not sure I completely understand the situation. ie_shim is used to enable HTML5 features in IE and is not at all related to responsive layouts. Fusion uses respond.js to create responsive features in IE.
if you do not want to include IE support for responsive layouts in your theme, you can disable the fusion_responsive_ie sub-module of Fusion Accelerator. Do you have that sub-module disabled and respond.js is still loading?
If you could let me know exactly what your theme settings are and provide a link to your site, I may be able to better troubleshoot the issue.
Comment #2
drupalninja99 CreditAttribution: drupalninja99 commentedSomething completely broke the layout in IE when I had responsive turned on. I can try to disable that fusion_responsive_ie module and see if that works. I guess it wasn't related to ie_shim.
Comment #3
drupalninja99 CreditAttribution: drupalninja99 commentedHas no one else reported ie problems with fusion responsive enabled?
Comment #4
drupalninja99 CreditAttribution: drupalninja99 commentedfusion_responsive_ie is disabled, I have tried disabling and enabling. I don't need any ie support, I just want ie to behave as normal and have responsive behavior for all other browsers/devices.
Comment #5
drupalninja99 CreditAttribution: drupalninja99 commentedIt doesn't looks like respond.js or css3-mediaqueries.js are loading.
Comment #6
drupalninja99 CreditAttribution: drupalninja99 commentedIn fusion_core template.php something is happening after this line that breaks IE
if (module_exists('fusion_accelerator') && theme_get_setting('responsive_enabled')) {
Comment #7
drupalninja99 CreditAttribution: drupalninja99 commentedIE doesn't like the openchurch_theme.responsive.grid.css even tho this looks like it works fine for other browsers.
If I add the grid12-960 '/themes/fusion/fusion_core/css/grid12-960.css' to an IE conditional, it works fine. I don't want to do a server-side IE check, so I am trying to figure out a way via an IE conditional or something to ignore the responsive stuff in IE.
Comment #8
drupalninja99 CreditAttribution: drupalninja99 commentedMy workaround for now is to force the theme to render the normal grid css in an ie conditional:
This way, in theory, makes IE always use the grid.
Comment #9
Leo Pitt CreditAttribution: Leo Pitt commentedI've been running into similar issues on a site I'm building. When css3-mediaqueries.js is loaded, the site is fine across IE7 and IE8.
The problem I've been having seems to be that css3-mediaqueries.js is not present in my page, despite all the instructions being followed.
Looking into fusion_responsive_ie.module code, there is a function fusion_responsive_ie_init() which is where the action takes place - I think it tests whether the browser is IE 6 - 8 and if so it loads the css3-mediaqueries.js library.
But doesn't hook_init only get called when the page isn't cached? And does this mean that the logic determining whether or not css3-mediaqueries.js is inserted gets bypassed when caching is off?
E.g.
Comment #10
Leo Pitt CreditAttribution: Leo Pitt commentedI've worked around by adding a conditional script to my html.tpl.php.
First in template.php:
And in html.tpl.php, just prior to the $scripts call:
Comment #11
Leo Pitt CreditAttribution: Leo Pitt commentedScratch that last post - turns out that IE was still behaving inconsistently.
In the end used the same approach as #8. :(
Comment #12
nielsonm CreditAttribution: nielsonm commentedThis happens for me when page caching is enabled. I just removed the logic that tests for the browser version and always adds the library if the module is enabled.