cbpye.net

So I was staring idly at my WordPress dashboard when I noticed a link to this video detailing some of the changes in WordPress 2.8.  Holy Shit.  They’ve got some nameless soft-spoken Englishman opening by comparing WordPress releases to jazz musicians, all while some jazz music is playing.  When the hell did my blogging software start shipping from the back room of a Starbucks?

All snarkiness aside, this looks good.  What remains to be seen, however, is whether or not they’ve had the good sense to stop shipping code that breaks standards compliance.  Just yesterday I had to manually edit the CSS file for Thickbox (no clue what it’s for, I only know it was breaking the CSS 2.1 compliance of my site).  Is that too much to ask?  I know that they can’t do anything about the javascripts or CSS files that third parties include with their plugins or themes (Sociable, I’m looking at YOU), but they could at least bother to be standards-compliant themselves (c’mon guys, set an example).

How’s this for a feature request?  Include a setting with WordPress that keeps track of whether or not I want to see standards-breaking plugins and themes when I search for them.  Is that so hard?  Just search the contents of whatever $developer uploads and scan any CSS files for nonsense like browser-specific element properties and CSS3-only properties and flag $developer’s package as bad and not worth using non-compliant, if appropriate.