I just finished reading the Selectutorial. (Actually, I’ve read it before but my CSS skills were not developed enough at the time to make any of it relevant enough to me to remember.) I must say, now that I fully understand it, it’s an different sort of excercise in frustration. Why? There are a lot of really, really useful CSS selectors that can’t be used. At least, not on a client’s site. With every new selector my excitement would build, until the summary: "…not supported by Windows Internet Explorer 5, 5.5 and 6, but are supported by most other standards-compliant browsers."
Think child selectors, adjacent sibling selectors, attribute selectors and the :before and :after pseudo-classes are just for CSS geeks? They could be regular part of your web-design diet, simplifying things like adjusting spacing conditionally depending on whether an element is right next to another. I could have used the attribute selectors to make only my little ‘off-site link’ images inline for a recent site instead of applying a class in the structural code to every freggin image tag!
It’s a shame that the worlds richest software company, fueled with hiring power and a presumably very well-educated and/or skilled workforce can’t make their browser standards compliant. If it wasn’t for Internet Explorer’s bad but predominant browser, things could be so much more efficient for everyone. Though I’ve applauded the relative dissapearance of "This site is best viewed in…" statement, I think I would now welcome "Best viewed in a standards compliant browser (
Internet Explorer, try