Jason Clark's Blog

Software, Hardware, whatever...

IE7 Wants.

Recently Microsoft announced IE7, rightfully so as FireFox is certainly gained a loyal following.  On AnandTech 38% of all browsers are Gecko based, while 36% are IE.   I'm still an IE user, have been since IE4.  FireFox is a decent browser, I just prefer IE for some unknown reason.   I've been doing a fair bit of JavaScript work lately, and admittedly I've been using FireFox to do all of my debugging.   FireFox has a wonderful JavaScript console built in, that details the location of the error, including file name for multiple JS files.  It is far and away better than the JS errors IE gives you, "there was an error on line 4 (usually the wrong line number)".   FireFox also does not spawn alerts on JS errors within a page by default, you have to use the Console to view those (the way it should be IMHO). 

 IE Team, if you are listening please put this functionality in IE, while you're at it give us tabbed browsing :)

Posted: Mar 03 2005, 11:16 AM by jclarknet | with 7 comment(s)

Comments

rick said:

Mozilla also has an excellent DOM Inspector. IEDocMon provides a similar DOM Inspector for IE, but it doesn't seem to work nearly as much. Plus, you can view the current styles of an HTML element and values of javascript objects.

I'm glad that they're releasing IE 7, but I have a feeling these needs won't make it...
# March 3, 2005 12:28 PM

Jerry Pisk said:

I agree with Rick, Mozilla also has a great JavaScript debugger, not just a simple console. And I'm also worried that the things that should happen in IE won't, that IE 7 will be a marketing release.

And once again - IE had tabbed browsing long, long time ago (3.x iirc). Mozilla/Firefox didn't invent it.
# March 3, 2005 1:41 PM

Jason Clark said:

"IE had tabbed browsing long, long time ago (3.x iirc). ", really? I wonder why it was removed, too usable? :)
# March 3, 2005 2:08 PM

Drew Marsh said:

IE (Windows really) has had a script debugger for as long as it's had script. Also if you use Visual Studio then you can use that for even richer debugging.

As for the DOM inspector, IE has had something similar for a while too written by a third party[2]. Though I will absolutely admit Mozilla's feature set is much nicer.

Cheers,
Drew

[1] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sdbug/Html/sdbug_1.asp
[2] http://www.cheztabor.com/IEDocMon/index.htm
# March 3, 2005 3:19 PM

Lola said:

Funny that you mention it, maybe the IE Team is actually listening.

I know a guy that had a blog site just like this one, he used to work for weightwatchers.com, then Microsoft saw his blog site and contacted him for a job, he got the job and is now in Seattle Washington working for some division of Microsoft.

So you never know, maybe they are reading it. But what I think IE shoudl really do is disable vbscript and activex. Becuase if they do not, then you will see more spam on your pc from IE 7.0.
# March 9, 2005 10:09 AM

TrackBack said:

^_^,Pretty Good!
# April 10, 2005 4:30 AM

josef said:

at the moment a have a javascript bug that *only*

appear in IE. Wich inserting alert()s i found the

postion anelement.appendChild(anotherElem).

But because all is ok, this doesnt help me.

So i am looking for the m$ scritping debugger.

And find out:

M$ has removed this form msdn.

The link above dont work!!!!!!(and all others)

<in bad mood>

Silly ununsable IE. I hope this browser is going

away fastly.

</>

# September 4, 2007 12:33 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)