search

kirubaharan12345 / blueprintcss

Automatically exported from code.google.com/p/blueprintcss
0 stars 0 forks source link

Don't remove the "column" class. Make it optional. #117

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

I took some advice regarding "blueprint best practices" once upon a time,
where I was advised that this would be good to do:

1. build a website with an earlier version of blueprint.
2. make columns out of all kinds of elements, not just the DIV tag. 
but...
3. upgrade to the most recent version
and unfortunately...
4. Now your XHTML no longer works :(

What is the expected output? What do you see instead?

Maybe I want a UL to act like a column. Maybe a P. How about a SPAN, even?
When you removed the need for the class named "column", I think you threw
the baby out with the bathwater. Try making the column class _optional_.

Adding the following CSS should do the trick.

.column, .span-1, .span-2, .span-3, .span-4, .span-5, .span-6, .span-7,
.span-8, .span-9, .span-10, .span-11, .span-12, span-13, .span-14,
.span-15, .span-16, .span-17, .span-18, .span-19, .span-20, .span-21,
.span-22, .span-23, .span-24 {float:left;margin-right:10px;}

Original issue reported on code.google.com by dylan.ki...@gmail.com on 17 Jul 2008 at 7:57

GoogleCodeExporter commented 8 years ago 
Perhaps that CSS belongs in a plugin?

Original comment by dylan.ki...@gmail.com on 17 Jul 2008 at 8:02

GoogleCodeExporter commented 8 years ago 
Copied over to
http://blueprintcss.lighthouseapp.com/projects/15318/tickets/31-don-t-remove-the
-column-class-make-it-optional#ticket-31-1

Original comment by horst.gu...@gmail.com on 13 Aug 2008 at 9:18