# Browser Wars: Insurrection?

When Dave Hyatt announced some of the cool new additions to WebCore to support Dashboard etc. - via "extensions" made to HTML - my first reaction was "Hey, that's cool!", followed rather quickly with "but, doesn't that break the standards?"

Things like the cool new attribute (announced here) on the input element work great, look awesome, but as a result, make the source page invalid XHTML-Transitional. Doh.

The new element (announced here), which gives you a place to draw bitmaps via javascript (and is used by the analog clock widget in Tiger's Dashboard), also very cool and useful, but not in the standard...

I'm glad to see I'm not alone in this feeling. Tim Bray just posted on this as well. If it bugs one of the godfathers of XML, it's got to be a real issue. I've implemented the new attribute in the search form on this weblog to try it out (you can only see it if you're using Tiger or Safari 1.3 Dev. Preview - otherwise it looks like a Plain Old text input box), so I'm not religious about it, but this sorta feels like the Netscape/IE "enhancements" of the '90s...

UPDATE: It looks like the Blosxom Autotrack plugin has run amok, hammering Dave's weblog over 300 times (180-ish on each of 2 posts on his weblog). Holy crap. I'm SO SORRY, Dave! I've deleted the Autotrack plugin. It won't happen again! I'm emailing Dave directly with apologies. Crap, this is so embarrasing...