On Wed, Mar 18, 2009 at 8:13 AM, Marc Funaro <[email protected]> wrote:
> Okay, but WHY should one have to define the margins on columns on the grid?
> It doesn't say anywhere in the wiki/documentation for blueprint that one
> would ever need to do this. This is an arbitrary fix to an arbitrary
> problem, and does NOT instill confidence in the framework.
>
The problem is not the grid itself, but the content you have inside
those columns, which have their own margins and are pushing the
columns below them. This is a very typical problem when doing layouts
with CSS. I found that by adding:
div {
margin-bottom:0 !important;
}
to the end of your stylesheet, all of the spaces disappeared. This is
a quick & dirty fix, and not something I would recommend for
production. Blueprint includes a class, "bottom", which removes margin
and padding from the bottom of any element. I would apply this class
to the elements that have these extra margins, after figuring out
which ones they are. But if you are in a hurry, well...
--
--
Christian Montoya
mappdev.com :: christianmontoya.net
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Blueprint CSS" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/blueprintcss?hl=en
-~----------~----~----~----~------~----~------~--~---
