- This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
Viewing 8 posts - 1 through 8 (of 8 total)
- The forum ‘CSS’ is closed to new topics and replies.
The forums ran from 2008-2020 and are now closed and viewable here as an archive.
Cant seem to get any transforms working in Chrome 12. Works in all other modern browsers. Link to test page: http://jimdavis.org/transtest1.html
What am I missing?
Where did you apply these classes:
.char1, .char2, .char3, .char4, .char5, .char6, .char7, .char8, .char9, .char10, .char11, .char12, .char14, .char15, .char16, .char17, .char18, .char19, .char20, .char21 {
-o-transform: rotate(25deg);
-moz-transform: rotate(25deg);
-ms-transform: rotate(25deg);
-webkit-transform: rotate(25deg);
transform: rotate(25deg);
}
I’m pretty sure this isn’t the best way to go about it.
The classes are created using lettering.js, a jQuery plugin. See http://letteringjs.com/.
This is where I got inspiration for the code. The page looks correct in Chrome 12 so I doubt there is a bug in Chrome. http://trentwalton.com/
@boringcode, I don’t believe that would be beneficial as that would require extra markup with span tags :/
@jimdavis, I didn’t notice the jquery script. I’ll look at it again.
Problem solved. Had to add display: inline-block to the span.
awesome, jim.
Well technically both of your suggestions are targeting the spans. Just one is using a class selector and one is using the type selector. With that, its obvious that both speed and markup would be benefited by using just the type selector. I say that because you would not have to write all of the classes to get the same result and the browser would not have to identify all of them separately. Even though they all have the same properties applied them.