JavaScript: The Definitive Guide, 3rd edition
by David Flanagan

This errata page lists errors outstanding in the most recent printing.  

If you have any error reports or technical questions, you can send them to
booktech@oreilly.com.  (Please specify the printing date of your copy.)

This page was updated June 28, 2001.

Here's the key to the markup:

        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification


Confirmed errors:


(9) top:
     
	"click on a image" 

should read 

     	"click on an image"


{230} Insert a new list item after "moveBy(), moveTo():

	open()
	    Open a new window.


<328> INFO:
Netscape Communicator 4.x has a known bug in that reloading a document does 
not always reload all objects in that document, espcially Layer objects.

The upshot is that in the Netscape implementation, the value of "this.layer" 
may be null or undefined.  In this case, using any of the defined functions in
the example (such as "getX") attempt to de-reference an undefined (or null) 
value, which causes Netscape Communicator to core-dump (or whatever this is 
called on windows).

As this is a popular browser, and this is an important example, I suggest that
the author should find a work-around, either recreate a Layer object (the 
quickest fix but with ugly results), or force a page reload (a slower method 
but will always work properly). 


(335) first complete paragraph:

	"Once the expiration date has past..."

"past" should be "passed".


{449} first code block: 
Change second line to:

   document.write('Today is: ' + d.toLocaleString());  // and print it out.


{509} INFO:
On this page, the author discusses the "form.action" property. I have found 
through testing that for the POST method of form submission to work, the 
"form.method" property must also be explicitly set, even if it is set within 
the original <FORM> tag.  There seems to be no problem if the form uses the 
GET method, but when I tried a "POST", all I got were 405 errors in both 
Netscape (4.6) & IE (4.01).

Setting the "method" property explicitly eliminated the problem.