IE8: Operation (now silently) Aborted

By crisp on Friday 25 April 2008 00:06 - Comments (7)
Categories: Browsers, Javascript, Views: 5154

The MSIE team proudly blogged about the 'fix' they made in IE8 for the dreaded "operation aborted" error that has plagued and confused many front-end developers (and end-users) the past decade or so.

Read more »

The versioning switch's default is incorrect

By crisp on Friday 22 February 2008 01:53 - Comments (2)
Categories: Browsers, Internet, Views: 3456

In fact, the whole versioning switch idea is bad to begin with. If you still don't understand why after my previous blog-entries and after having read for instance Jeremy Keith's reasoning on AListApart (and failed to see the flaws in Jeffrey Zeldman's entry) here's a break-down of the arguments against the versioning switch and against the proposed default (== IE7 mode):

Read more »

Some thoughts on HTML5's getElementsByClassName

By crisp on Monday 11 February 2008 23:24 - Comments (8)
Category: Javascript, Views: 2897

HTML5 will bring us some really cool things, not only in terms of new markup features but also in terms of extended features for forms and a very handy DOM extension in the form of a native (and thus lightning fast) getElementsByClassName method.

Read more »

The road to HTML5: conformance of HTML4 documents

By crisp on Sunday 03 February 2008 23:37 - Comments (3)
Categories: HTML, Tweakers.net, Views: 3191

Recently I ran the Tweakers.net frontpage through the (experimental) HTML5 validator (by Henri Sivonen) to see how well we are being forwards-compatible. The result wasn't too bad, just 13 errors.

Read more »

Using the HTML5 doctype prematurely "considered harmful"

By crisp on Sunday 27 January 2008 16:13 - Comments (3)
Categories: Browsers, HTML, Internet, Views: 4618

There has been a lot of fuss around Microsoft's ludicrous idea of freezing IE into IE7's quirksmode rendering for the (un)foreseeable future unless you specify some proprietary meta-tag in all your documents. There was however a tiny shimmer of good faith in this huge anti-competitive move when Chris Wilson, MSIE's productmanager, offered that this lock-in might not affect documents using some new doctype or mimetype that is currently unsupported by IE.

By the way, the "considered harmful" in the title is intentional even though it has been abused as a populistic phrase throughout the years: it seems fitting since no one less than Eric Meyer once wrote an essay on the subject of why "considered harmful" can be considered harmful by itself ;)

Read more »