I've spent a lot of time trying to learn and use CSS. After all, the W3C says that all my old favorite tags are deprecated in favor of CSS and it does sound like a good idea -- cleaner code and all that.
After more than a few browser releases, CSS is starting to drive me crazy. My only solution on most sites has been to use browser detection and then write different .css files for the two main browsers.
However, I'm not posting just to complain -- I know other people have to be in this boat, and I just found this page [richinstyle.com] with a very intelligent collection of Netscape 4 CSS bugs and workarounds. In fact, this site has a great collection [richinstyle.com] of all kinds of bugs.
I'm hoping it can help me stop talking to my carpet. Actually I'm feeling better already. I just learned that setting font sizes in px is a good thing to do -- it's less buggy and it keeps an appropriate size rendered no matter what the screen resolution. Who would have thought?
Rich in Style is of course a great site. There is just a touch of controversy how the testing is done. Some in the css community are at odds with a few of the findings on RichInStyle. If interested, check some of the Usenet groups on authoring and CSS. There are a few of the higher ups that are less than 100% pleased with the site. I think it is a great resource - second only to the W3C itself and possibly Webreview.com [style.webreview.com].
This site [css.nu] is coming to my rescue a lot lately. The information is gleaned from the css newsgroups, and the workarounds presented seem to be very accurate.
It's the first place I got help with "loss of style" on Netscape. That is, sometimes after a table tag or form tag, Netscape loses all style and defaults to user preferences. Can be very ugly!
The workaraound is to use redundant selectors -- something I would never have thought of doing on my own.
Another nice tidbit -- the problem: 13pt and 14pt type are rendered the same size. The fix: declare 14.1pt type. Again, I never would have tried it.
Even after five years, it's still very hard for me to adapt to the slushy way a lot of web coding works. I majored in math, and have an assumption that coding should be logically rigorous. Maybe someday.