I've been experimenting with using the semantic classes feature of compress.rb and it doesn't seem to be working properly. Here's an example of a simple page using standard, non-semantic Blueprint:
http://charlesroper.com/lab/bp3col/non-semantic/ Then I apply the following settings.yml file using compress.rb (note that I am using a custom layout): https://gist.github.com/175356/294659fb9f7212d25a74bb12d6b92492f35306ae ... and the layout goes haywire: http://charlesroper.com/lab/bp3col/semantic/ After a good long debugging session, I have isolated the problem to the .push-4 class on the #primary div. This addes a right float and a funky margin which, in the semantic version, gets overridden again by the div.span-x classes, which are more specific and thus override and properties defined by the .push class. I fixed this problem by changing my id's to classes in settings.yml: https://gist.github.com/175356/c99a1a9cd79004488cc4014bdc39cea6265903aa ... and I obviously added the appropriate classes to the HTML. Whew. http://charlesroper.com/lab/bp3col/fixed-semantic2/ Could this behaviour be classes as a bug? It certainly felt like one for a long time and took quite a bit of will-power to actually solve from my perspective, considering Blueprint is supposed to save me these sorts of headaches (I just can't resist a challenge, though). 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;} 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 -~----------~----~----~----~------~----~------~--~---
