Closed (fixed)
Project:
Zen
Version:
6.x-1.0-beta3
Component:
IE Problems
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Jan 2009 at 05:40 UTC
Updated:
28 Jul 2010 at 15:30 UTC
Hi everybody. I'm having a problem with my Zen sub-theme in IE7. The site is http://www.charlestonelementary.net. On the front page as well as the "Classroom Index" page the closure blocks section is floating on top of teaser nodes. I've found that if I open a new tab and scroll up and down, it will put the closure blocks section back where it should be when I go back to the tab.
I am using the jquery eye candy module (curvy corners only) but this problem persists even with that disabled and caches cleared. The class ".nodes-teaser" has no rules on any of the style sheets. In short I'm stumped and I'm hoping somebody out there might be able to point me in the right direction.
Comments
Comment #1
autodidactic commentedI tried to isolate the problem but no luck. To make the problem apparent without completely destroying the layout of the site, I put a syndicate block in the closure region and styled it with a left border. Incidentally I tried moving the block to the footer region and the same problem persists. It seems anything after the "main" div gets stacked on top of the content-area. This only when teasers and pagers are listed. This is strange and has me frustrated beyond belief. Any help offered would be appreciated.
Comment #2
autodidactic commentedAlright I've isolated the problem in IE7. The "#page" div is not expanding with the content. What is peculiar is that this only affects pages with node teasers. I've tried adding height:100% and/or position:relative rules to the #page,#page-inner divs but to no avail. I freakin hate IE. It seems like the wheel has to be reinvented for that stupid browser every time.
Update: I fixed it. I floated the #main and clear:both; on the #closure-blocks and all is well now in IE7.
Comment #3
Diecilab commentedThanks!!! It worked! I lost many hours trying to find a fix.
Comment #4
akalata commented