By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,700 Members | 1,512 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,700 IT Pros & Developers. It's quick & easy.

javascript debugger for MIE 6.0

P: n/a
I am working on a piece of javaScript code and using MIE 6.0. I have and
error and I would like to use a debugger to locate the error. Is there a
debugger for MIE? How do I turn the debugger on for MIE? Where can I
locate the debugger for MEI 6.0? I am using WIN 98 operating system.
Jul 20 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
On Wed, 18 Feb 2004 02:06:38 GMT, alonzo <le****@aol.com> wrote:
I am working on a piece of javaScript code and using MIE 6.0. I have and
error and I would like to use a debugger to locate the error. Is there a
debugger for MIE? How do I turn the debugger on for MIE? Where can I
locate the debugger for MEI 6.0? I am using WIN 98 operating system.


Script debugging with IE (any version) is quite difficult to do. It tends
not to indicate where the error occurred properly, and the messages it
gives are vague.

To access script debugging, open "Internet Settings" from the Control
Panel, click the "Advanced" tab and make sure that the option "Disable
script debugging" under "Browsing" is unchecked. When an error occurs, a
yellow warning icon will appear in the bottom left part of the status bar.
Double click this to display a pop-up, then click the "Details" button for
the information.

If you have the option, use Opera, Netscape or Mozilla (all free) to debug
your pages. You're more likely to catch errors (they are more
standards-compliant), and they show much more detailed information. For
Opera, the JavaScript debugging console is under "Window" > "Special" >
"JavaScript console". With Netscape and Mozilla, the console is under
"Tools" > "Web Development" > "JavaScript Console". Netscape and Mozilla
also provide other tools for page debugging.

Mike

--
Michael Winter
M.******@blueyonder.co.invalid (replace ".invalid" with ".uk" to reply)
Jul 20 '05 #2

P: n/a
> I am working on a piece of javaScript code and using MIE 6.0. I have and
error and I would like to use a debugger to locate the error. Is there a
debugger for MIE? How do I turn the debugger on for MIE? Where can I
locate the debugger for MEI 6.0? I am using WIN 98 operating system.


Microsoft's Visual Studio contains a very good JavaScript debugger. I
use it every day. There is a free version available at
msdn.microsoft.com, but it is crippled. You might be able to find and
old, cheap copy of Visual J++ 6 or Interdev 6.
Jul 20 '05 #3

P: n/a
In article <OM*****************@fe1.texas.rr.com>, le****@aol.com
enlightened us with...
I am working on a piece of javaScript code and using MIE 6.0. I have and
error and I would like to use a debugger to locate the error. Is there a
debugger for MIE? How do I turn the debugger on for MIE? Where can I
locate the debugger for MEI 6.0? I am using WIN 98 operating system.


There is a debugger for download at microsoft. You need to set IE to
display errors and to offer the debug option after you install it.

Big link:
http://www.microsoft.com/downloads/d...E606E71F-BA7F-
471E-A57D-F2216D81EC3D&displaylang=en

--
--
~kaeli~
A plateau is a high form of flattery.
http://www.ipwebdesign.net/wildAtHeart
http://www.ipwebdesign.net/kaelisSpace

Jul 20 '05 #4

P: n/a
In article <op**************@news-text.blueyonder.co.uk>,
M.******@blueyonder.co.invalid enlightened us with...

Script debugging with IE (any version) is quite difficult to do.


No it's not. You just need their debugger for anything useful.

http://www.microsoft.com/downloads/d...E606E71F-BA7F-
471E-A57D-F2216D81EC3D&displaylang=en

--
--
~kaeli~
A plateau is a high form of flattery.
http://www.ipwebdesign.net/wildAtHeart
http://www.ipwebdesign.net/kaelisSpace

Jul 20 '05 #5

P: n/a
On Wed, 18 Feb 2004 08:37:47 -0600, kaeli <ti******@NOSPAM.comcast.net>
wrote:
In article <op**************@news-text.blueyonder.co.uk>,
M.******@blueyonder.co.invalid enlightened us with...
Script debugging with IE (any version) is quite difficult to do.


No it's not. You just need their debugger for anything useful.


Hopefully, they'll integrate it into the next release of IE. It would
certainly make a lot of sense: I expect that *relatively* few people know
it's available.

Mike

--
Michael Winter
M.******@blueyonder.co.invalid (replace ".invalid" with ".uk" to reply)
Jul 20 '05 #6

P: n/a
I am sorry to post a message here not related to the first topic.

I wonder what other method I can use to replace javascript as the
client side scripting. I am not using ASP.NET for the server side, and
try to use javascript for the client side. Is it a good combo and are
they working well with each other? sometimes i am confused if i should
use the server or the client to program a task.

Any opinions are appreciated.
Michael Winter <M.******@blueyonder.co.invalid> wrote in message news:<op**************@news-text.blueyonder.co.uk>...
On Wed, 18 Feb 2004 02:06:38 GMT, alonzo <le****@aol.com> wrote:
I am working on a piece of javaScript code and using MIE 6.0. I have and
error and I would like to use a debugger to locate the error. Is there a
debugger for MIE? How do I turn the debugger on for MIE? Where can I
locate the debugger for MEI 6.0? I am using WIN 98 operating system.


Script debugging with IE (any version) is quite difficult to do. It tends
not to indicate where the error occurred properly, and the messages it
gives are vague.

To access script debugging, open "Internet Settings" from the Control
Panel, click the "Advanced" tab and make sure that the option "Disable
script debugging" under "Browsing" is unchecked. When an error occurs, a
yellow warning icon will appear in the bottom left part of the status bar.
Double click this to display a pop-up, then click the "Details" button for
the information.

If you have the option, use Opera, Netscape or Mozilla (all free) to debug
your pages. You're more likely to catch errors (they are more
standards-compliant), and they show much more detailed information. For
Opera, the JavaScript debugging console is under "Window" > "Special" >
"JavaScript console". With Netscape and Mozilla, the console is under
"Tools" > "Web Development" > "JavaScript Console". Netscape and Mozilla
also provide other tools for page debugging.

Mike

Jul 20 '05 #7

P: n/a
In article <b0**************************@posting.google.com >,
al*********@yahoo.com enlightened us with...
I am sorry to post a message here not related to the first topic.

Then why didn't you start a new thread? ;)
I wonder what other method I can use to replace javascript as the
client side scripting.
Unless all your users have IE, there isn't a replacement for client-side
javascript. By that I mean that only IE supports other client-side
scripting languages. IE supports VBScript. Other browsers do not.
If you meant replacing client-side scripting with server-side scripting,
that depends on the task.
I am not using ASP.NET for the server side,
You're NOT using it?
What ARE you using, if anything, for server-side scripting?
and
try to use javascript for the client side. Is it a good combo and are
they working well with each other?
There is no connection between the server-side scripting language of
choice and javascript. One runs on the server. The client never even
sees it. The client code never sees the server code. It doesn't care
what generated the page. It sees plain html (or css, javascript, etc)
text.

(note: runat=server is not all that common and the client doesn't do
anything with it besides make a request to the server to get the block
processed)

client request -> server -> server gets page and runs it through
processing if needed -> client gets page -> client-side script runs

The client can't even tell that the page was generated via server-side
scripting, much less what language did it. YOU can tell because it is
convention to use .asp, .php, etc extensions, but those are certainly
not a requirement. If I configured my server a certain way, I could have
PHP pages that have a .html extension. You'd have no idea they were PHP
pages.
sometimes i am confused if i should
use the server or the client to program a task.


Unless the script deals with changing existing content on the client or
depends on the client for something, there is no need to use client-side
scripting. Your server is much faster, more than likely, than someone's
browser. If you have a server-side scripting capability, use it.

The server knows nothing about the client, thus, you cannot use server-
side scripting for anything that *dynamically* (that is, it doesn't post
back to the server) changes client content (DHTML stuff like moving
layers around or client-side validation) or anything that relies on
client information (positioning content based on resolution, etc).

There is a difference between dynamically generating html, which is done
server-side most commonly (like generating content based on DB queries),
and dynamic html (DHTML), which usually refers to things moving or
changing on the page without server interaction.

Note that javascript cannot by itself talk to the server. ActiveX or COM
can, but just your "normal" garden-variety cross-browser javascript
cannot.

--
--
~kaeli~
No one is listening until you make a mistake.
http://www.ipwebdesign.net/wildAtHeart
http://www.ipwebdesign.net/kaelisSpace

Jul 20 '05 #8

P: n/a
For a simplistic way of "printing" out debug information that work in
HTML & Javascript, see my article:
http://groups.google.com/groups?hl=e....earthlink.net

Re: Debug - Your own console
& be sure to use the second article.

Robert
Jul 20 '05 #9

P: n/a
kaeli wrote:
The client can't even tell that the page was generated via server-side
scripting, much less what language did it. YOU can tell because it is
convention to use .asp, .php, etc extensions, but those are certainly
not a requirement. If I configured my server a certain way, I could have
PHP pages that have a .html extension. You'd have no idea they were PHP
pages.


True, see for example <http://pointedears.de.vu/mozilla/nightly/buggy>.
The best way to access resources is not what you call "convention" but
to omit any "extensions" (i.e. suffixes) in URIs that may indicate the
technology used since a) such information could be exploited, attacking
known security vulnerabilities and b) "Cool URIs don't change", even if
the server-side technology changes:

<http://www.w3.org/QA/Tips/uri-choose>
PointedEars
Jul 20 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.