Internet Explorer's representation of VKitties

• Me: Hey, Internet Explorer, can you load an SVG for me?
• IE: A what?
• Me: Create an EMBED element with the source ‘/data/kitten.svg’
• IE: Ok.
• Me: Now append it to the sidebar.
• IE: Put what where?
• Me: *sigh* Create an EMBED element with the source ‘/data/kitten.svg’ as a variable called ‘e’
• IE: Ok.
• Me: Put the element represented by the variable ‘e’ at the bottom of the last element child of the element represented by the id ‘sidebar’.
• IE: Ok.
• Me: That’s not what it’s supposed to look like!
• IE: ERROR 6704632: Unknown variable “That’s”
• Me: AAAARGH
• IE: ERROR 824893: Unknown variable “AAAARGH”
• Me: Set the ‘fill’ attribute of the element represented by the id ‘kittenFill’ in the content document of the window represented by the variable called ‘e’ to ‘#f00′
• IE: Ok.
• Me: // Nothing changed…
• IE: Ok.

And now, a few pictures:

Microsoft may harm your computer. This is not a fake!

Internet Explorer visits the VKitty Humane Society

Firefox visits the VKitty Humane Society

However, unlike the other Browser Warz competitions, the browsers in this competition will be facing other versions of their own kind before going on to face the winners of each individual competition.

There are 4 things that the browsers will be scored on in this leg of the competition:

• CSS errors (Is the purple header there?  Does the body of the page match up with the header?  Is the footer matching?  Are the horizontal rules hidden?)
• JavaScript errors (Are there any?  How bad are they?)
• Speed of the 3 tests (How fast were each of the three tests?  How long did it take 5 repeats of each test to occur?)
• Total time taken on the tests (How many seconds did it take?)

The 26 browsers are split up into 5 categories:

• Internet Explorer (7 browsers, page 2)
• Firefox (4 browsers, page 3)
• Opera (6 browsers, page 4)
• Netscape (7 browsers, page 5)
• Other (2 browsers, page 6)

This competition, because it is so long, is divided into pages to reduce loading time.

To pass test 2, the browser has to:

1. Correctly render the page from last time, except not gzipped.
2. Read base64 encoded data and parse it as JavaScript.
3. Do 10 million empty loops, 5 million Math.random() calls, and 500 thousand empty eval() calls as soon as the page loads.
4. Respond to a double click event.
5. Ask for permission to do memory-intensive scripts.
6. Do 250 million empty loops, 125 million Math.random() calls, and 12.5 million empty eval() calls in under 10 minutes.
7. Not crash during the time that it does step 3, although not responding for up to 5 minutes at a time is ok.

The results:

Safari went the fastest:  256.564 seconds (4.276 minutes)

Next in speed was Opera, with a time of 275.92 seconds (4.599 minutes)

And then comes Firefox, with a time of 371.446 seconds (6.191 minutes)

Internet Explorer was disqualified because it did not render the page, nor did it respond to the double click event when I gave it a .html copy of the test.  I was curious, however, so I used the javascript: protocol and tested it.  It came in faster than opera!

As always, you can download the test.  Here it is: Browser Warz test 2