Closed (fixed)
Project:
Clean
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Dec 2009 at 21:21 UTC
Updated:
14 Jan 2010 at 12:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
psynaptic commentedI did some layout fixes yesterday so hopefully this was fixed with those changes. Could you update and let me know?
Comment #2
joachim commentedNope, no sign of a width on #content with no sidebars.
Comment #3
joachim commentedComment #4
psynaptic commentedDid you just look at the CSS without testing in the browser? There is no need to explicitely set a width and the theme collapses based on columns. When there are no sidebars the content div takes up the full width. Only on pages with sidebars does the content div need an explicit width.
Please can you confirm you can see a problem in the browser?
Comment #5
joachim commentedIf the node being shown with no sidebars is quite short, just a few lines of text, then its width is LESS than the maximum. And then any styling like borders of background is wrong.
Eg:
Which is more or less what a client wanted.
Comment #6
psynaptic commentedI have taken a screenshot of the theme with no sidebars highlighting the #content div (using Firebug).
As you can see, it takes up the full width available. This is so that pages with wide content e.g. admin pages, node forms, etc. can be given the full width.
I'm not entirely sure I understand what you are saying but it sounds like it is something that should be specific to that individual site.
Comment #7
joachim commentedYup, fixed in the lastest from CVS: this change fixed it:
.no-sidebars #content {
float:none;
}