Sitemeter has an announcement on their blog that they have worked around the weird, non-standard behavior of IE6 & IE7.
I didn’t have the problem because I put the Sitemeter code in a neutral place on my template, as opposed to the places that freaked out the garbage browser from MS.
The real solution is to get a browser that conforms to the standards that everyone else uses and doesn’t screw up peoples’ designs.
On-line Opinion Magazine featuring annoyed rumblings from the leading edge of the Baby Boom firmly tied to a reality-based world.
Established: 21 November 2004
The opinions expressed in Comments are those of the individuals making them. Truly absurd comments and opinions are subject to being cruelly mocked, but "flame wars" will take place on someone else's dime.
Your first comment, all comments with extensive links, and random comments that the software decides it doesn't like for no discernible reason will be held for moderation.
[Be aware that for unknown reasons the software rejects comments shorter than 15 characters, so if you want to leave a short comment fill the gap with periods ........]
1 comment
I am extremely sympathetic to the developers at Sitemeter. No matter which browser one is running a script under, finding a specific element under the document object, when the elements were generated on-the-fly and may not have unique id’s, is a royal PITA, and I consider it a design flaw in the DOM. (Unfortunately, they didn’t ask me. 🙂 ) That may or may not be the specific problem Sitemeter was facing; I didn’t look. But it may have been something of that nature. You are correct that a good standard, reliably adhered to by all platforms, would help a lot.