Internet Explorer 6 and 7 both have problems with cookies in at least one situation when you use an iframe and the src redirects a lot around the same domain. This was painful to debug, because it worked perfectly in Opera and Firefox ... ultimately it meant a network trace and a fine-toothed comb.

So I've been working on a desktop app to debug ie. It's not able to do all that much yet, and I'm wondering how much effort this idea merits? I don't think it'll ever do the 'inspect element' thing FireBug does. But I can build an as-rendered dom tree, and probably tweak elements after the document is loaded. Would people use the software if it had this, and/or other features?

Browser Component:


Browse History:

Since there are so few tools to help debug IE problems, this would, in fact, be helpful. The IE developer toolbar is ok, but it's nothing like Firebug or even the Web Developer extension for FF.

You know, it bugs the, well, something, out of me that when you refresh the page, IE's developer toolbar looses your place in the dom tree! I know it's kind of difficult to avoid that, but Firebug keeps your place.

Forrest, if there was a tool like the firebug dom inspector for IE, trust me, I'd even pay for that.

It would be so much useful....
I'm not that versed in "desktop programming", but I've already thought about it for a java practicing development, and I would if I had not already a lot of time eaters...

Originally Posted by tripy

Forrest, if there was a tool like the firebug dom inspector for IE, trust me, I'd even pay for that.

That's great to hear! I'm actually not going to charge for this ... I'll probably wind up publishing the source code. But I'd love to see it become popular.

I don't think I'll be able to do breakpoints, but it looks like I should be able to do other nifty stuff at runtime. If you have any suggestions as to what you'd like to see, I'm all ears.

More than breakpoints, I'd love to be able to see the properties of an js object.

I've been pulling my hairs out when trying to find what kind of object was this when having an action triggered via an event in js...
And for those who are wondering, it's the HTML element in firefox, and it's the event call in IE