On Aug 26, 8:29 am, Charles Roper <[email protected]> wrote:
> Would adding specific id selectors to the .column, div.span-1, [...]
> {float:left;margin-right:20px;} rule help? E.g.
>
> .column, div.span-1, div#span-1, [...] {float:left;margin-right:20px;}
Ahh, the penny just dropped as to why seemingly redundant declarations
are made in the settings.yml example file:
semantic_classes:
"#footer, #header": ".span-24, div.span-24"
"#content": ".span-17, div.span-17, div.colborder"
"#extra-content": ".span-6, div.span-6"
"div#navigation": "div.span_24, .span-24"
"div.section, div.entry, .feeds": ".span-6 div.span-6"
Adding, say, div.span-24 overrides other less specific declarations,
such as .push. Got it now.
The resulting CSS is quite messy, though:
/* semantic class names */
#footer, #header {float:left;margin-right:20px;width:940px;margin-
right:0;}
#primary {float:left;margin-right:20px;width:460px;margin:0 -240px
1.5em 240px;float:right;position:relative;}
#secondary {float:left;margin-right:20px;width:220px;margin-
left:-720px;float:left;position:relative;}
#tertiary {margin-right:0;padding-right:0;float:left;margin-right:
20px;margin-right:0;width:220px;}
There is some redundancy and duplication in there. It could do with a
parser that mops up any redundant property declarations from left to
right. For example, in #tertiary, the first margin-right can go and
the second one also. It's not critical, but would make things neater
and less, uh, itchy for anal retentives like me. :)
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
-~----------~----~----~----~------~----~------~--~---
