Height problem: side-bars vs. main-content lineup
madjoe - October 13, 2006 - 00:40
| Project: | Democratica |
| Version: | 4.7.x-1.x-dev |
| Component: | Stylesheets |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
There is an issue with presenting some of the content from various modules and views in this template. Take a look at the screenshot... Within the main-content there is a control panel content, but I've noticed that the location of control panel content depends on the maximum height of the content from left/right side-bar...
| Attachment | Size |
|---|---|
| screenshot_29.png | 67.32 KB |
#1
The same thing happens while editing nodes....
#2
This is so annoying... hm! I can't locate the problem even with my DevTool plugin for Firefox.
#3
Yeah, there's another issue on this type of problem. It is pretty frustrating.
#4
After reading http://drupal.org/node/25192 and http://drupal.org/node/38426, I studied the style.css file and found the following section:
/*<group=Profile Styles>*/.profile {
_position: relative;
_height: 1%;
clear: none; /* override drupal.css clear:both which causes whitespace */
}
This gave me the clue I needed to fix the problem.
HOW TO FIX
Add the following code to the style.css file:
.node-form .standard {clear: none; /* override drupal.css clear:both which causes whitespace */
}
This fixed the problem for me.
#5
There are other "pages" which also exhibit this behavior, such as the bottom half of the Democratica theme settings page. Therefore I also added the following code to style.css:
.theme-settings-bottom {clear: none; /* override drupal.css clear:both which causes whitespace */
}
NOTE: There may be other classes in the stock drupal.css file that need similar overriding by Democratica's style.css file.
#6
Nice Lafflam!! These fixed both the FF and IE problems I was having! I owe you my first born!
#7
Retraction of Update #5 above
Update #5 above breaks the general themes settings page in Democratica. I recommend not using the code from Update #5.
Following further testing, Update #4 seems to solve the original problem and continues to work fine.
#8
Problem still exists... Did you check: admin/themes/settings?
Take a look at the attached image.