I’ve used display: inline-block on personal projects for form labels, buttons and just this morning applied the style to fix a bug. Without the display: inline-block I would’ve had to write 2-3 lines of css code and we all know less is better!

Firefox 2 was a great browser in it’s time but people have to start upgrading if they want a better web experience but the problem is that they don’t know they can have that unless someone tells them. For that I reason I strongly believe that we, designers and developers’ have to take the initiative and have some sort of display message on page load telling users to upgrade – much like the one running on this site.

I noticed something similar on our templates but it used classes a bit more…and I sort of prefer that (even though it isn’t as semantic).

Reason being that whilst we can use conditional comments to include / exclude HTML or CSS hacks for IE there’s no way to target a specific Firefox, and what’s the score with Firefox 3 and the -moz prefix? I’d expect it to work in the same way but is it a hack for a non-problem?

We can always do that server side and to be honest I don’t know why it was a problem for that site. I will ask why it was not allowed, presumably for performances reasons but I can’t work out what that would be. Will have to ask.

Will definitely consider it for future sites though. It’s a solution for a common problem and CSS problems should be solved with CSS not by chucking more classes at an element