
you are the weakest link... good-bye!
For those of you who are wondering, yes, SiteMeter is, in fact, breaking yours and every other webpage it is embedded into (update) so long as you are using IE 7, 6, and probably 5.5. No idea why. No idea how to fix it.
Or, rather, I do know one way to fix it - comment out your SiteMeter code: Just put "<*!--" before it and "--*>" after it (minus the *s), and all will be well. The above page tells you what to look for by way of code specifically.
As for information about this interesting little catastrophe, ironically enough, SiteMeter's own site is... down. Funny, that. Keep an eye on that first link, though - they seem to be keeping tabs on the situation. Then, once it clears up, just go back and remove the comment tags from around your SiteMeter code, and things will be back to normal. If nothing else, it is a lot easier than straight-up deleting the code and having to go find it again.
Update 2: Sitemeter appears to be up and running again, and has been reimplemented on this site without any noticeable errors. Good to hear they were able to fix it.
Trackposted to Perri Nelson's Website
1 TrackBacks
Listed below are links to blogs that reference this entry: you are the weakest link... good-bye! .
TrackBack URL for this entry: http://www.wallsofthecity.net/mt-tb.cgi/1437
...it's a shame to have to turn off some perfectly good utilities because Microsoft can't seem to fix bugs rather than explain them away. Read More

As disclaimers go, this one is pretty
tame - no traps here. All writings, posts, and ideas
contained within the "wallsofthecity.net" domain are the
sole intellectual property of either 



*heh*
Had to fire up a VM with WinXP and load Internet Exploder to see the error(s). (I also got a flash player error.)
In my normal browser, Opera 9.52, no error(s).
Firedfox? No problem(s).
I wish more sites would do as Sitemeter has apparently done and code pages strictly accordin g to standards so more sites would refuse to looad in Internet Exploder.
*shrug* As I repeatedly tell the fanboys of all of the other browsers out there, I have used IE for as long as I have been on the internet, and I have never once had a single virus, or a significant security problem outside of tracking cookies. The problem is not that the browser is unsecure, the problem is that people are idiots, and no uber-secure browser will fix that.
If Sitemeter has gone a route that keeps their code from loading in IE, they are going to have a lot of rightfully upset people on their hands... not to mention this was the wrong way to go about it.
The browser's "unsecure" nature is not so much the problem (can be dealt with in other ways). The problem is that its rendering engine is not standards-compliant: it regularly "breaks" standards-compliant html/CSS in ways that b rowsers that attempt standards-compliance do not.
"[W]rong way to go about it"? Well, I guess so! Silly of them to put up standards-compliant code that's easily rendered! Downright stupid.
Of course, if Me$$y$oft made any effort at all at being a team player and even checking what their rendering engine does to well-crafted, standards-compliant code that darned near every other browser (NOT using Internet Exploder's crappy, slow, buggy, bloated rendering engine) can render without a hitch, then I'd not dump on Me$$y$oft's crappy, slow, buggy, bloated code.
Keep on using Internet Exploder, but please, please, for the sake of your family (unless you have LOADS of life in surance) do NOT buy a "Microsoft Car".
*heh*
You must visit other sites than I do, because I have never had a rendering problem with IE that I can recall, even on sites with those cute little "This site verified to be HTML whateverthehell," buttons at the bottom of their pages. *shrug* I use what works.
Yeah, and that is still the wrong way to go about it - you announce to people you are making this sudden and potentially disastrous change, give them time to find some other way to go about their lives, and then convert over. Me, I think this is just some manner of accident, or some hacker enjoying himself. But if it comes out that this was an intentional move on the part of Sitemeter, I will most assuredly stop using them, and strongly campaign against them. Something tells me you would feel the same way if they suddenly wrote and implemented, without any warning, code that crashes Opera (if such a thing exists).
IE may be "slow, buggy, bloated" and other things, but Firefox once crashed my computer when it was not even running, and, personally, I notice no execution or browsing speed increases with Opera, so, again, I use what works, and see no need to change to something that, apparently, works as well as what I already use.
The problem is a bug in Internet Explorer. Encourage your users to get Firefox, Opera, or even Safari. Microsoft refuses to fix (they just mask the bug in IE 8) this bug.
Try doing a floating footer with absolute or relative positioning in CSS and see how it renders in IE, then compare it to Firefox or Opera. I can give you a VERY SIMPLE example page... http://drkphoenix.com/
It renders correctly in Firefox and Opera, using STANDARD css. It does not render correctly in Internet Explorer.