Thursday, August 07, 2008 10:55 AM
by
ascarb
Why the IE Developer Toolbar sucks
In the last throws of a testing sprint I started to go through my check list for all of the Atalasoft web components in IE (browser versions had been divied up for testing, and I got IE). Not too long ago I read an article about IE's developer toolbar, at the time I thought "Oh, good. I can debug in IE now too -- sweet!" All had been going along fine now till now. After the latest version in the web controls had been added I started to see the following exception when run in IE,
Microsoft JScript runtime error: Object doesn't support this property or method
when it hits this function,
function ParseDoc(doc)
{
var aRules = GatherRulesFromDoc(doc);
collSelectors = parser.Parse(aRules);
// Set quirks mode if necessary
if("BackCompat" == doc.compatMode)
{
for(var i = 0; i < collSelectors.Count; i++)
{
collSelectors.item(i).SetQuirksMode(true);
}
}
}
Which was popped up every time I ran any script associated with the web controls, and after a few pop ups annotations added to the image disappeared. Given that this function is nowhere to be found in any of Atalasoft's web libraries a quick search on the error brought up this rather helpful post that pointed to the culprit -- IE Developer Toolbar. You can also just disable it, as I did, as there is a perfectly good and safe debugging tool already available -- FireBug.
Yes, debugging and testing tool do change the system, but good ones never destroy data.