Closed (duplicate)
Project:
Zen
Version:
7.x-5.1
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 May 2012 at 12:31 UTC
Updated:
18 Dec 2012 at 10:25 UTC
Jump to comment: Most recent file
Comments
Comment #1
rvdtuin commentedThe bottom region is also missing in IE 8
Comment #2
rvdtuin commentedIn IE9 the navigation region is in its correct place.
the bottom region is not visible in IE9 and Chrome
Comment #3
jtwalters commentedDo you have CSS aggregation enabled? i.e.
$conf['preprocess_css'] = 1;IE less than 9 requires CSS aggregation to have respond.js work properly.
Comment #4
rvdtuin commentedThanks for the reply. I will look in to it.
I think this will take some time because I am fairly new at drupal and zen.
Comment #5
johnalbinThere was a problem with the navigation styling in 5.0. Upgrade to 5.1, follow the upgrade steps outlined at http://drupal.org/node/1588228 and let me know if this fixes the issue.
Comment #6
gary hbs commentedI have the same issue using a Commerce Kickstart distribution and a Zen sub-theme on my front page. I have not been able to find out why the region changes places and so my interim solution is to add a top region to the front page panel (panels) and add a navigation block (in my case a Superfish). This results in IE displaying the Superfish menus correctly but in Chrome there is a white band where the nav section used to be.
Comment #7
zeppfan commentedHi Jt Walters,
IE less than 9 requires CSS aggregation to have respond.js work properly.
I can confirm that aggregating the CSS does indeed work. I did this via the interface itself via:
Configuration | Performance
Many thanks
Comment #8
echoz commentedComment #10
Fiable.biz commentedThis should of course be documented. I propose to write what to do in the Starterkit's Readme file because Zen is not a theme aimed to be used without modification, so every user is supposed to use Staterkit, and aggregation is typically something one does after creating and installing one's subtheme.
Here enclosed is my proposal. I added a (non optional) step at the end, and changed the "Optional steps" line to "Optional step 6", "Optional step 7" and "Optional step 8".
Comment #11
echoz commentedThe problem is that during development we don't want css aggregation on because it makes css debugging pretty much impossible. If we continue to use respond.js, more documentation would be helpful, thank you for your efforts, although it seems like this is pending #1539682: Turn off Respond.js by default, use .lt-ie9 rules for IE8 layouts
Comment #12
Fiable.biz commentedSince no work seems to have been done for nearly 3 months on the bug you quote, which is "unassigned", and nobody is forced to develop with IE, I suggest we modify the file README.txt, which would save people hours of useless work (as for me last week), and we would modify that file back for Zen 7.x-5.3 once the bug will get corrected.
Comment #13
silentbob commentedSame Problem for me with Safari on ios6 and iphone 4. Navigation is pushed below content.
Comment #14
echoz commented@silentbob this is the default when on the narrowest viewport (mobile) the main navigation appears below the content.
Comment #15
Fiable.biz commentedThis is intended not to clutter small screens with big menus. If the menu is too big and the page would begin by the menu, the visitor might no even see he has changed page.
Comment #16
echoz commentedDocumentation has been committed from #1608216: IE8 and below will not respect CSS media queries with "Aggregate and compress CSS files" disabled. Marking this a duplicate.