I get the picture. But I think I may conclude that doctype is what
really matters here. Thanks!
Christian Montoya escribió:
On Wed, Jun 16, 2010 at 1:40 PM, Daniel Peraza <[email protected]> wrote:
Oh! I'm sorry guys for not answering these posts before, but I already
fixed the problem. Both changing the doctype to strict, and adding the
column class helped me. But I would like to know why did this work, because
I thought that was subtle details with no, or little importance. Specially
adding the column class, because in the blueprint's css source code, .column
seems to be the same that .span-X.
Using the STRICT doctype triggers a different rendering mode, and
there are many differences between rendering modes, one being the
default line-height and vertical-alignment of various elements. As for
adding the column class, I think it just affected the inheritance
priority of certain rules. Sorry if all that doesn't make sense, it's
hard to explain.
--
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.
