Saturday afternoon, SiteMeter put up this notice on their blog, explaining the problem I blogged about in the wee hours Saturday morning. I’ve reinstalled my SiteMeter code; if you still get the error, refresh again (what I did) or clear your cache.
Reading various reactions to the problem (and I admit mine was definitely born of frustration, after having seemingly resolved a problem ongoing for months), there was certainly a lot of venom directed at Internet Explorer and Microsoft, but there was also some pretty significant backlash against SiteMeter.
While I’m not in love with IE (actually, I don’t like it very much at all, but version 7 is a million times better than 6), blaming MS/IE for something that SiteMeter caused seems a bit extreme. Of course, the argument can be made that if IE were written properly, SiteMeter’s gaffe wouldn’t have affected it. Conversely, one can also argue that something wonky was going on with javascript, so IE was acting properly within the scope of how it (attempts to) secures the browser against external attacks.
I’m not expert enough, by a long shot, to be able to point a finger. Granted, SiteMeter “oopsed” and actually resolved the issue in less than 24 hours. Of course, for sites that have a very heavy IE readership (and yes, there are many), those were a pretty disastrous 12-14 hours or so, in terms of page views and hits. On the other hand, Firefox and Opera1 didn’t choke on SiteMeter’s back-end revision: A fairly powerful argument in their favor.
But the bottom line is, the issue is resolved and my readers who use IE6 or 7 can once again view the Aerie in all its avian glory.
Join 746 eclectic readers.
Join the flock: Now 412 strong!
Tami (30)
Mazil (13)
Iris (9)
Bre (8)
Kimberly (4)
krizzlybear (4)
{ 3 comments }
Opera is a very nice browser; it’s faster than Firefox, although not quite as minimalist. The major reason I stopped using it was because I couldn’t figure out how to make it switch tabs in physical order instead of temporal order.
… which is exactly what Firefox is going to do in 3.1 with no option of turning it off. *sigh*
Incidentally, you might be interested in this: http://browsershots.org/
Itsnoteasy’s last blog post: I Think I’ll Go For a Walk
@ Its: Interesting site; waiting for my screenshots to upload now. Next week I’m planning to run the site against HTML & CSS verifier sites.
Not sure I understand exactly what you mean by temporal vs. physical tab-switch order, though. I will say that FF 3.0 introduced some behaviors I wish I COULD change. I may also look at Flock, just because it’s there.
Incidentally, I notice Opera doesn’t recognize the “color” attribute of the HR tag, either.
Kestrel’s last blog post: SiteMeter – Internet Explorer Problem Resolved
I agree, Opera is a nice browser, but in the long run Firefox is the one with all the plugins I’m addicted to!
Comments on this entry are closed.