On Aug 26, 11:51 am, Josh Clayton <[email protected]> wrote: > There are plenty of block-level elements within Blueprint that have a > margin-bottom of 1.5em (http://gist.github.com/175454). That said, I > don't know if .push-X classes are wrong (having the margin-bottom) or > if .span-X, .pull-X, etc are wrong and *should* have the margin- > bottom. > > I think we should look a bit closer and determine which would be > better as a baseline.
Given that .span-x, .pull-x, prepend-x and append-x do not have bottom margins, and that pull-x are in the same family of grid-centric rules used for structure, I would say pull-x should not have a bottom margin for consistency's sake. What's more, with the .prepend-bottom and .append-top rules, one can easily add the correct vertically- rhythmic margin, should one need to. Getting rid of margins such as this is what the reset CSS is designed to do, and so it seems a bit backward to go about re-adding them, especially when you consider you're likely to want to cancel them out again most of the time! And of course it seems to cause confusion. However, push-x also adds a float:right ... So, what's *that* for? Charles --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
