You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to customize the prev/next buttons (with, say, an icon), it is also required to recreate about half the styles associated with .icon-next and .icon-prev. This is because these styles also include
.icon-prev {
&:before {
content:'\2039';// SINGLE LEFT-POINTING ANGLE QUOTATION MARK (U+2039)
}
}
.icon-next {
&:before {
content:'\203a';// SINGLE RIGHT-POINTING ANGLE QUOTATION MARK (U+203A)
}
}
I suggest additional classes created .icon-prev-indicator and .icon-next-indicator that just has the content associated with it. these names would avoid any existing icon conflict both in glyphicons and font awesome.
+1 Just came across this because I use FontAwesome instead of glyphicon. I had to add the .glyphicon* classes even though I don't use the icons, just to get the positioning styles.
Unfortunately we cannot change the class names until v4. We could deprecate these, but I shy away from that approach given it leaves busted and duplicate code lying around.
In order to customize the prev/next buttons (with, say, an icon), it is also required to recreate about half the styles associated with
.icon-next
and.icon-prev
. This is because these styles also includeI suggest additional classes created
.icon-prev-indicator
and.icon-next-indicator
that just has the content associated with it. these names would avoid any existing icon conflict both in glyphicons and font awesome.this is how it currently works (ripped from the sample site)
http://jsfiddle.net/Y9HnH/
how i think it should work
http://jsfiddle.net/fwqvK/
A similar complaint could be made about background styles applied via
.carousel-control.left
and.carousel-control.right
The text was updated successfully, but these errors were encountered: