On Sat, Jul 3, 2010 at 8:22 AM, Cristian Bichis <[email protected]> wrote:
> - it's more recommended to have all the css side included on only one file, > rather than split on 2 files. This leads to slower loading + if you take a > look on SE tools like Google Webmaster Tools all recommend having only one > file in place This leads to slower loading *IN IE ONLY*. Also, you don't have to use ie.css if you don't want. > - i am not sure how we going to use BluePrint ie.css component for the case > of html based emails (emails with html multipart)... Blueprint is not for emails. Emails require a very different approach. > There are ways to simplify the css loading to actually have only one file > loaded for the same media ? As far as i checked the other css framework > doesn't include separated files for IE. Which CSS frameworks did you check? Are they any good? To be honest, you could take all the rules in ie.css and put them in screen.css, using IE hacks to hide them from other browsers... but the developers of Blueprint insisted on ensuring that Blueprint would be as standards compliant as possible, so they used a conditional comment. It also means that the core files are not littered with ugly IE hacks and ie.css can be maintained, updated, etc. without affecting other files. -- -- 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.
