Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #21166 > unrolled thread

FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05)

Back to article view | Back to comp.lang.javascript

Contents

  FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05) "FAQ server" <javascript@dotinternet.be> - 2013-09-04 23:00 +0000
    Re: FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05) Christoph Michael Becker <cmbecker69@arcor.de> - 2013-09-05 01:26 +0200
      Re: FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-06 13:03 +0200
        Re: FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05) Christoph Michael Becker <cmbecker69@arcor.de> - 2013-09-07 00:55 +0200
          Re: FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-10-02 16:01 +0200

#21166 — FAQ Topic - How do I get my browser to report javascript errors? (2013-09-05)

-----------------------------------------------------------------------
FAQ Topic - How do I get my browser to report javascript
errors?
-----------------------------------------------------------------------

There are debugging tools for many browsers. Learn to use them all.

Windows

Fiddler [ref 1].
Fiddler is an HTTP Debugging proxy (it won't find script
errors). Fiddler logs HTTP activity, like Firebug's Net
tab, but can be attached to any browser running on Windows.

Windows IE
Microsoft Script Editor. Included with Visual Studio or Microsoft
Word 2003 (discontinued in Office 2007).
To enable,
`Tools`, `Internet Options`, `Advanced`, and uncheck
`Disable Script Debugging`. After enabling Script Debugging,
a `Script Debugger` option will appear in the `View` menu.

http://jibbering.com/faq/IETester [ref 2] for testing IE 5.5- IE8.
http://jibbering.com/faq/CompanionJS [ref 3] `console` for IE.

_Note:_ For debugging scripts in IE, the Microsoft Script _Editor_
is recommended. However, if not available, the Microsoft Script Debugger [ref 4] may be somewhat helpful.

Internet Explorer Developer Toolbar [ref 5]

To report errors: Wait until a little yellow
triangle appears at the left end of the status bar, double click
on it and, when the error dialog box appears, check the "Always
show errors" checkbox it contains.

Or, `Internet Options`, `Advanced`, deselect `"Disable Script Debugging"`,
select `"Display a notification ..."`.

Firefox

`Tools > Error console` (`Ctrl` + `Shift` + `j`).

Firebug [ref 6]

YSlow [ref 7].
YSlow analyzes web pages and tells you why they're slow
based on Yahoo's rules for high performance web sites.

Lori [ref 8]
Lori or Life-of-request info, is useful for troubleshooting
server response and page load time.

Web Developer Toolbar [ref 9].

Cookie Watcher [ref 10].

XPather [ref 11].
XPath generator, editor and inspector.

Opera

Tools > Advanced > Error console

Introduction to Opera Dragonfly [ref 12]

Safari

To display the `Develop` menu in Safari 3.1 or higher, select
the checkbox labeled "Show Develop menu in menu bar" in
Safari's `Advanced` Preferences panel.

Safari Web Inspector [ref 13]

Chrome

JavaScript Console: click the `Page` menu icon and select
`Developer > JavaScript Console`. From here, you'll be
able to view errors in the JavaScript execution, and enter
additional javascript commands to execute.

JavaScript Debugger: available as `Page` menu icon > `Developer`
> Debug JavaScript, the debugger provides a command prompt from which you
can set breakpoints, backtrace, and more. Type `help` at the debugger
command line to get started.

  * Google Chrome Script Debugging [ref 14]

  * Developer Tools for Google Chrome [ref 15]

  * http://jibbering.com/faq/Tools for Eclipse Users [ref 16]

Mac IE

Use the Preferences dialog.

References:
-----------

[1] http://www.fiddlertool.com/fiddler/
[2] http://www.my-debugbar.com/wiki/IETester/HomePage
[3] http://www.my-debugbar.com/wiki/CompanionJS/HomePage
[4] http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en
[5] http://www.microsoft.com/downloads/details.aspx?FamilyID=e59c3964-672d-4511-bb3e-2d5e1db91038&displaylang=en
[6] http://getfirebug.com/
[7] https://addons.mozilla.org/en-US/firefox/addon/5369
[8] https://addons.mozilla.org/en-US/firefox/addon/1743
[9] https://addons.mozilla.org/en-US/firefox/addon/60
[10] https://addons.mozilla.org/en-US/firefox/addon/1201
[11] https://addons.mozilla.org/en-US/firefox/addon/1192
[12] http://dev.opera.com/articles/view/introduction-to-opera-dragonfly/
[13] http://trac.webkit.org/wiki/Web%20Inspector
[14] http://www.google.com/chrome/intl/en/webmasters-faq.html#jsexec
[15] http://blog.chromium.org/2009/06/developer-tools-for-google-chrome.html
[16] http://blog.chromium.org/2009/08/google-chrome-developer-tools-for.html


The complete comp.lang.javascript FAQ is at
http://jibbering.com/faq/

-- 

The sendings of these daily posts are proficiently hosted
by http://www.pair.com.

[toc] | [next] | [standalone]

#21167

FAQ server wrote:

> -----------------------------------------------------------------------
> FAQ Topic - How do I get my browser to report javascript
> errors?
> -----------------------------------------------------------------------
> 
> There are debugging tools for many browsers. Learn to use them all.

[snip]

> References:
> -----------

[snip]

<FAQENTRY>

[17] <http://devtoolsecrets.com/>

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#21174

Christoph Michael Becker wrote:

> FAQ server wrote:
>> -----------------------------------------------------------------------
>> FAQ Topic - How do I get my browser to report javascript
>> errors?
>> -----------------------------------------------------------------------
>> 
>> There are debugging tools for many browsers. Learn to use them all.
> 
> [snip]
> 
>> References:
>> -----------
> 
> [snip]
> 
> <FAQENTRY>

Hm, apparently the FAQENTRY method is not dead yet :)  However, although as 
I can see now I had committed myself to considering “<FAQENTRY>” indeed, I 
would much prefer to consider (such) suggestions only in FAQ threads that I 
would start, based on suggestions received via e-mail. [1]

What do you think?
 
> [17] <http://devtoolsecrets.com/>

Thanks.  Added, and heading fixed.

(Please read [1] before your next suggestion.)

However, unless the person regularly posting the sections starts using the 
(new, maintained) “FAQ for comp.lang.javascript”¹ instead of the (old, 
unmaintained) “comp.lang.javascript FAQ”², the change will not be reflected 
in the daily FAQ postings.

Although I could probably set up a posting script for the new FAQ, it does 
not make sense to have two differing FAQ postings per day (if at all).

_________
[1] <news:1432633.0Ca1GCPGyj@PointedEars.de>

¹ <http://jibbering.com/faq/>
² <http://PointedEars.de/faq>
-- 
PointedEars, ed.

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#21176

Thomas 'PointedEars' Lahn wrote:

> Christoph Michael Becker wrote:
> 
>> <FAQENTRY>
> 
> Hm, apparently the FAQENTRY method is not dead yet :)  However, although as 
> I can see now I had committed myself to considering “<FAQENTRY>” indeed, I 
> would much prefer to consider (such) suggestions only in FAQ threads that I 
> would start, based on suggestions received via e-mail. [1]
> 
> What do you think?

Hmm, actually I *would* prefer that such suggestions could be made
directly by posting to the newsgroup, but that would require you to read
(or at least scan) all posts, what seems to be undue.  I don't know, if
there has been ever been such a "FAQ robot" mentioned in the FAQ, and
what has become of it.  If the program would be available and working,
it might be used again.

> However, unless the person regularly posting the sections starts using the 
> (new, maintained) “FAQ for comp.lang.javascript”¹ instead of the (old, 
> unmaintained) “comp.lang.javascript FAQ”², the change will not be reflected 
> in the daily FAQ postings.
> 
> Although I could probably set up a posting script for the new FAQ, it does 
> not make sense to have two differing FAQ postings per day (if at all).

I agree that having two *different* FAQ posters doesn't make sense.
However, I quite like the idea of having such postings--be it only for
the purpose to make new readers of the group aware that there is a FAQ,
which should be read.  Long time regulars who feel distracted by these
posts could easily killfile the FAQ server.

How this should be handled, however, again raises the question about a
new maintainer of the c.l.js FAQ...  Unfortunately, it seems there are
several regulars who rather prefer to stick with an unmaintained and
out-dated FAQ than to agree to let the FAQ being maintained by someone
they dislike, because he seems to be too harsh.  If this disqualifies
someone for being the maintainer of the FAQ, the FAQ should be
rewritten.  For instance:

| How do I detect Opera/Safari/IE?
|
| The short answer: Don't do that.

should be changed to:

| How do I detect Opera/Safari/IE?
|
| Dear Reader,
| you might consider this a bad idea, because it may cause a variety
| of problems.  Of course, we have to assume that you are an
| experienced developer, and that you know exactly what you're doing,
| so just use the navigator.userAgent property to detect the user's
| browser.
|
| If your time permits, you are invited to read some humble opinions
| in the following, why this might not be reliable.  Otherwise feel
| free to ignore the rest of this section.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#21500

Christoph Michael Becker wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Christoph Michael Becker wrote:
>>> <FAQENTRY>
>> 
>> Hm, apparently the FAQENTRY method is not dead yet :)  However, although
>> as I can see now I had committed myself to considering “<FAQENTRY>”
>> indeed, I would much prefer to consider (such) suggestions only in FAQ
>> threads that I would start, based on suggestions received via e-mail. [1]
>> 
>> What do you think?
> 
> Hmm, actually I *would* prefer that such suggestions could be made
> directly by posting to the newsgroup, but that would require you to read
> (or at least scan) all posts, what seems to be undue.  I don't know, if
> there has been ever been such a "FAQ robot" mentioned in the FAQ, and
> what has become of it.  If the program would be available and working,
> it might be used again.

It would be infinitely easier for everyone if such postings would *also* 
have to be tagged in the Subject header field value to be considered, like 
“[FAQ] …”, because then a newsreader would suffice (for me to look for such 
postings, and for those who are not interested in those discussions at the 
moment to filter them out).  The customary discipline in changing Subjects 
would probably be required so that threads are left intact when postings are 
threaded by Subject:

  foo
  '--Re: foo
     '--[FAQ] bar (was: foo)
        '--Re: [FAQ] bar

OTOH, this also indicates that both the FAQ robot and the Subject approach 
would miss the goal of reducing FAQ discussions in the newsgroup.

> […]  Unfortunately, it seems there are
> several regulars who rather prefer to stick with an unmaintained and
> out-dated FAQ than to agree to let the FAQ being maintained by someone
> they dislike, because he seems to be too harsh.  If this disqualifies
> someone for being the maintainer of the FAQ, the FAQ should be
> rewritten.  For instance:
> 
> | How do I detect Opera/Safari/IE?
> |
> | The short answer: Don't do that.
> 
> should be changed to:
> 
> | How do I detect Opera/Safari/IE?
> |
> | Dear Reader,
> | you might consider this a bad idea, because it may cause a variety
> | of problems.  Of course, we have to assume that you are an
> | experienced developer, and that you know exactly what you're doing,
> | so just use the navigator.userAgent property to detect the user's
> | browser.
> |
> | If your time permits, you are invited to read some humble opinions
> | in the following, why this might not be reliable.  Otherwise feel
> | free to ignore the rest of this section.

YMMD :)

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web