Being a css guy these days is not very exciting. Up until a few years ago, the css scene was brewing with activity, trying to overcome various browser bugs and css shortcomings. Every month there was a new method that fixed some or other nasty issue, saving us a whole lot of stress and cursing. But those days are over. Browsers have improved, most bugs are fixed (though some non-crucial ones remain) and peace has settled over the land of css once again.
Related Submissions:
- A Web Developer’s Responsibility Because browser bugs are so frustrating and such a burden on top of normal development it should be the responsibility of every web developer to...
- Floatitis Part 1 : An Introduction Floats, the nightmare of everyone starting out with css. Sure they are helpful, but are they worth all the bugs and cursing and exceptions on...
- RMSforms – A Flexible CSS Forms Framework To alleviate these issues and to help designers / developers avoid unwanted stress, I took a crack at developing “RMSforms”, a CSS forms framework. To...
- 10 IE Compatibility Problems That You Might Not Have Realised Over the years, ocProducts has maintained a private list of issues in different web browsers, and if there’s one thing that is consistent it is...
- Fluid Images One of the really solid criticisms lobbied against my Fluid Grids article for ALA was that all of my examples were pretty text-heavy. As a...