Sitepoint.com recently published a somewhat anti-climatic article espousing the CSS shortcomings of IE7, more than a year after the product was launched, and about two years after IE7’s beta was released for testing.
I can’t help but feel that some of this frustration aimed at Microsoft is unfair. The developers of IE7 have always stated that CSS2 support was their goal but also that IE7 would never pass the Acid test.
IE7 fixed the bugs we bitched about the most: Peekaboo, double-floating margin, box model, PNG support, etc. Apparently they even visited positioniseverything.net to get the real deal scoop on what geeks were complaining about. (Perhaps if we’d been more united in our call for standards-compliance, they might have listened, but that’s another story.)
Read the rest of this entry »
Web standards?!? We don’t need no stinkin’ web standards!
Some startling statistics, according to a study conducted by Rene Saarsoo on web coding practices. He (or his bot rather) combed over a million pages from sites listed in the Open Directory Project and found some disturbing trends:
- Only 39% of the pages use a valid DOCTYPE (how the hell do people miss this, most HTML programs these days insert one by default);
- A whopping 2.58% of the pages were HTML or XHTML valid;
- The fourth most common error amongst that sea of invalidity was forgetting to close a tag;
- The top five most common CSS declarations: color, font-size, font-family, text-decoration and font-weight, otherwise known as the stuff people use to style up their myspace pages.
You can check out his study here.
Useless trivia-that-means-absolutely-nothing-unless-you’re-bored-and-unemployed: I was retooling my page to make it XHTML-compliant yesterday. What does that mean? Well, according to the World Wide Web Consortium, it’s because of two reasons…
Read the rest of this entry »
