Comments on: Internet Explorer Developer Toolbar

By: Shravan Manda

Shravan Manda — Tue, 20 Nov 2007 18:11:09 +0000

This thing does not allow to edit like Firebug does. I have used the previous version of this and it used to allow creating new attributes but not this one. The new attributes dissapear just like that. I cant imagine this the best they have come up with???.

By: nemetral

nemetral — Mon, 27 Aug 2007 21:46:23 +0000

Of course it can’t compete with FireFox Web Developer Toolbar, let alone Firebug.. still, it’s better than nothing and I thank the elements outlining features for saving me much time in finetuning the designs!

By: Maarten Hurkens

Maarten Hurkens — Thu, 26 Jul 2007 09:33:16 +0000

Yup, firefox one is mucho better

By: Webdev

Webdev — Tue, 24 Jul 2007 11:37:57 +0000

It is quite limited in terms of functionality. Its no match for web developer toolbar for firefox. Its 100 times better than this one.

By: Mike Maier

Mike Maier — Wed, 06 Jun 2007 23:39:49 +0000

Cannot seem to trace a style to a specific file or block? What?

By: John

John — Mon, 21 May 2007 13:43:18 +0000

This tool is fake. Doesnt work at all… :/

By: Rizqi Ahmad

Rizqi Ahmad — Sun, 20 May 2007 17:28:11 +0000

it causes my IE to crash unexpectedly

By: Michael Geary

Michael Geary — Thu, 17 May 2007 22:52:43 +0000

I give up. Stupid comment form. Ajaxians, you know people would like to be able to post code samples in comments here!

By: Michael Geary

Michael Geary — Thu, 17 May 2007 22:51:22 +0000

Yeah, Steve, I’m familiar with Windows Script Editor too. IIRC it does lack one of my favorite features in Visual Studio: intraline JavaScript single stepping and breakpoints.

As an example, suppose you are single stepping through this contrived one-liner:

for( var i = 0; i

By: sartre

sartre — Thu, 17 May 2007 21:11:20 +0000

Speaking of, whats up with this activex control trying to run everytime I come to the ajaxian homepage.

By: steve apel

steve apel — Thu, 17 May 2007 16:29:56 +0000

Michael, I agree that the Visual Studio JS Debugger is a great tool (it’s all I used before Firebug). And there is a free version – Windows Script Editor is free and looks/operates nearly identically.

Sadly, this toolbar release offers nothing over the lame version we currently have.

By: Shuo Geng

Shuo Geng — Thu, 17 May 2007 16:12:11 +0000

Play it a little bit, not that bad. It is better than nothing.

By: Michael Geary

Michael Geary — Thu, 17 May 2007 15:49:47 +0000

And yes, Fiddler is a GREAT tool. Also, it works with any browser, not just IE. You simply have to set the proxy manually in other browsers.

By: Michael Geary

Michael Geary — Thu, 17 May 2007 15:48:56 +0000

The IE developer toolbar does have one feature I really like: the ability to edit any attribute of a DOM element.

Regarding JavaScript debugging, it’s unfortunate that there isn’t a free version of Microsoft Visual Studio’s JavaScript debugger. It’s the best JS debugger I’ve used.

By: Jeffrey Robbins

Jeffrey Robbins — Thu, 17 May 2007 15:17:03 +0000

I have been using the IE developer toolbar for about a year now. While the DOM traversal is semi-useful the rest of the functionality seems to be a pathetic attempt to mimic Firebug. And while I am on the topic of pathetic attempts, lets not forget to mention the IE script debugger.

The only useful tool I use with IE is fiddler (http://www.fiddlertool.com/).

By: Marco

Marco — Thu, 17 May 2007 14:23:56 +0000

There is nothing about javascript errors, the real problem on ExploDer…

By: RD

RD — Thu, 17 May 2007 10:06:37 +0000

Unfortunately there is no change since the last version (beta3). And besides it being useless to me, it has been known to mysteriously close my browser.

All I really want from them is something as effect as the FF error console.