Commentary

Dave Methvin
 

SiteMeter Fiasco Shows Developer Disregard For Internet Explorer

Friday night was full of late-night fireworks as Web sites and blogs using SiteMeter delivered an "Operation aborted" dialog box to every Internet Explorer user on every page. The problem was finally fixed on Saturday morning, but by then there were a whole lot of angry (former?) SiteMeter users.

Friday night was full of late-night fireworks as Web sites and blogs using SiteMeter delivered an "Operation aborted" dialog box to every Internet Explorer user on every page. The problem was finally fixed on Saturday morning, but by then there were a whole lot of angry (former?) SiteMeter users.There isn't any mystery as to the cause of these error messages. It was an unfixed, long-standing, well-known, well-documented bug in Internet Explorer. The SiteMeter script that Web sites insert into their pages tickled that bug. Even SiteMeter's own home page generated the error if you visited it with IE.

There's also no doubt where the blame lies for this fiasco. SiteMeter pushed out a change to its scripts late on a Friday and it wasn't tested adequately -- if at all - -on Internet Explorer. I can just see the developers rushing to finish before the weekend, then making their work live before heading out the door to celebrate with a beer. Visitors to SiteMeter's client sites were the first to notice the problem, but couldn't do anything other than complain; it seems like many sites didn't realize the problems were due to the SiteMeter code until early Saturday.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I do have some sympathy for SiteMeter's developers. Most likely, they all use Firefox as their main browser, for good reason. Yes, Internet Explorer still represents around 70% of the traffic on the Web, although it varies significantly by Web site. IE7 fixed some of the worst problems in IE6, but Web developers are still left to work around bugs like this one. That huge market share means that it's impossible ignore IE7 bugs, or even IE6 bugs, in a Web site design. If you ever want to put any Web developer or designer into an instant bad mood, say "Your site doesn't quite look right in Internet Explorer." Then run away before you get hurt.

There is a serious lack of quality tools for design and development in IE. Microsoft's IE Developer Toolbar does a respectable job for tweaking CSS, but its ancient Script Debugger is no match for what Firefox has with Firebug. There are dozens of other Firefox plugins that make development fast and easy; that's why Web site developers prefer the "minority" Web browser by a landslide.

With IE8, Microsoft seems to be making another big push to bring its browser up to par with Firefox. Let's hope it kills the "Operation Aborted" bug and delivers some up-to-date developer tools. We'll know it succeeded if SiteMeter releases an update that doesn't work with Firefox.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links