Hi Chris,
you´re right when it comes to my border-right class. It doesn´t make sense
in a second case. The blueprint border-class is exactly the same in it´s
result. So i would suggest to leave border-right out, but: i´m still trying
to convince you on the border-classes. They would make the
boder/colborder/hr classes and definitions just complete. I´m using borders,
border-top and border-bottom in my basic-stylesheets and some other useful
stuff too. I´m posting it here to hear what you (and anyone else) think of
it.
Note: They are not only bp-related/have anything to do with a grid.
----------------------------
/* To avoid dotted lines attached by browsers – they won´t work everywhere
but in a lot of cases */
a, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a { text-decoration: none; border: none;
outline: none; }
button::-moz-focus-inner, input[type="reset"]::-moz-focus-inner,
input[type="button"]::-moz-focus-inner,
input[type="submit"]::-moz-focus-inner, input[type="file"] >
input[type="button"]::-moz-focus-inner { border: none; padding: 0; }
.white-text, .white-text * { color: #fff; }
.kern-neg { letter-spacing: -0.1em /* reduce kerning in special cases with
large heading */ }
.kern-pos { letter-spacing: 0.1em }
----------------------------
Btw: (saw that while writing:) append-top und prepend-bottom have margin
instead of padding added. Maybe it would be a good idea to change this to
padding and add another two classes for margin: push-top, push-bottom and
maybe (but i can´t think of any case they would be needed) pull-top and
pull-bottom.
That´s it.
--
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.
