Errata

Shouldn't figure 2-2's "Add" node be "add"?

Note from the Author or Editor:
In Figure 2-2, please change "Add" (uppercase) to "add" (lowercase)

In the sentence

"This process continues until either the identifier is found or there are no more variable objects to search, in which case the identifier is deemed to be undefined."

the word "undefined" should probably read "undeclared", to avoid confusion.

Note from the Author or Editor:
In the sentence, "This process continues until either the identifier is found or there are no more variable objects to search, in which case the identifier is deemed to be undefined."

Please change "undefined" to "undeclared".

In the sentence:

Instead of accessing a global variables three times, that number is cut down to one.

"variables" should be "variable".

Note from the Author or Editor:
In the sentence, "Instead of accessing a global variables three times, that number is cut down to one." the word "variables" should be changed to "variable".

In the sentence:

This event handler is a closure, as it is created when the assignEvents() is executed and can access the id variable from the containing scope.

It should be:

... when assignEvents() is executed ...

or

... when the assignEvents() function is executed ...

Note from the Author or Editor:
In the sentence beginning, "This event handler is a closure, as it is created when the assignEvents() is executed" remove the word "the".

"because title is an object instance" should read "because title is an instance property".

Note from the Author or Editor:
Please change "because title is an object instance" to "because title is an instance property" in the 4th paragraph.

In the sentence:

To be more accurate, you should be careful to use object member only when necessary.

"member" should be "members"

Note from the Author or Editor:
In the sentence, "To be more accurate, you should be careful to use object member only when necessary.", the word "member" should be "members".

There is a sentence that reads, "But looping over an array is faster that looping over a collection...". I think "than" was meant instead of "that".

Note from the Author or Editor:
In the sentence, beginning "But looping over an array is faster that looping over a collection", replace "that" with "than".

"because there are usually less items to loop over" should be "because there are usually fewer items to loop over"

Note from the Author or Editor:
Please change

"because there are usually less items to loop over"

to

"because there are usually fewer items to loop over"

"The benefit of using the Selectors API over iterating instead of the results of getElementsByTagName()"

should be

"The benefit of using the Selectors API over iterating the results of getElementsByTagName()"

i.e. remove "instead of"

Note from the Author or Editor:
Please change the caption for Figure 3-6 to read:

The benefit of using the Selectors API instead of iterating over the results of getElementsByTagName()

1. Take the element off of the document flow
should be
1. Take the element out of the document flow

Note from the Author or Editor:
Please change

1. Take the element off of the document flow

to

1. Take the element out of the document flow

Use of drag and drop proxies is mentioned in the summary, but not earlier in the chapter.

Note from the Author or Editor:
The bullet that says:

Position absolutely during animations, and use drag and drop proxies.

Should be changed to:

Position absolutely during animations.

In the sentence:

The fourth edition of ECMA-262 introduced a new method on the native array object call forEach().

"call" should be "called"

Note from the Author or Editor:
In the sentence, "The fourth edition of ECMA-262 introduced a new method on the native array object call forEach()", the word "call" should be changed to "called".

In the sentence:

Since the factorial of 6 is equal to 6 multiplied by the factorial 5, the factorial of 5 is being calculated twice.

"multiplied by the factorial 5" should be "multiplied by the factorial of 5"

Note from the Author or Editor:
In the sentence, "Since the factorial of 6 is equal to 6 multiplied by the factorial 5, the factorial of 5 is being calculated twice." the phrase "multiplied by the factorial 5" should be "multiplied by the factorial of 5".

For clarity, there should not be a space between memfactorial and (n-1).

Note from the Author or Editor:
In second code example, change this line:

memfactorial.cache[n] = n * memfactorial (n-1);

To:

memfactorial.cache[n] = n * memfactorial(n-1);

(Remove the space between memfactorial and (n-1).

There is a sentence that reads, "Generic memoization of this type is less optimal that manually updating the algorithm..." I believe "that" should be "than".

Note from the Author or Editor:
In the sentence beginning, "Generic memoization of this type is less optimal that manually updating the algorithm" the word "that" should be "than".

Change "and teaching you how to write regular expressions that take advantage of this" to "and showing you how to write regular expressions that take advantage of this".

The sentence

"In other browsers, the difference is less significant or is optimized differently altogether".

Should be changed to:

"In other browsers, the difference is less significant or is optimized away altogether."

In the sentence:

Browsers place limits on the amount of time that JavaScript take to execute.

"take" should be "takes"

Note from the Author or Editor:
In the sentence, "Browsers place limits on the amount of time that JavaScript take to execute." the word "take" should be changed to "takes".

Comment wrapped across line, making last word of comment a variable reference. Both need extra // on wrapped line

Note from the Author or Editor:
Change this line in the example:

req.setRequestHeader('X-Requested-With', 'XMLHttpRequest'); // Set a request
header.


to be this:

req.setRequestHeader('X-Requested-With', 'XMLHttpRequest');

And change this line:

var responseHeaders = req.getAllResponseHeaders(); // Get the response
headers.

To be this:

var responseHeaders = req.getAllResponseHeaders();

The sentence reads, "As you can see, using favoring attributes over child tags...".

"using" should be removed.

Note from the Author or Editor:
In the sentence, ""As you can see, using favoring attributes over child tags...", the word "using" should be removed.

The sentence reads, "Keep in mind the main different between this format and all others..."

"different" should be "difference"

Note from the Author or Editor:
In the sentence, "Keep in mind the main different between this format and all others...", the word "different" should be "difference".

The sentence reads, "When creating you own custom format..."

"you" should be "your"

Note from the Author or Editor:
In the sentence, "When creating you own custom format...", the word "you" should be changed to "your".

msxml_progid has an unnecessary trailing comma in its array declaration.

Note from the Author or Editor:
This line:

'MSXML2.XMLHTTP.3.0', // Doesn't support readyState 3

should be changed to (remove comma):

'MSXML2.XMLHTTP.3.0' // Doesn't support readyState 3

Please keep the indentation exactly the same.

Existing errata for this page is also wrong - the last line in the examples should be:

alert(result4.toString(2)); //"-11010"

not
alert(resul2.toString(2)); //"-11010"
or
alert(result2.toString(2)); //"-11010"

Note from the Author or Editor:
Please change the last two lines of the second example code on the page from:

var result = ~ 25; //-26
alert(resul2.toString(2)); //"-11010"

To:

var result4 = ~ 25; //-26
alert(result4.toString(2)); //"-11010"

Please make sure the // line up with the previous lines of code in the example.

The actual result of this code:

var result3 = 25 ^ 3; //26
alert(result3.toString(2)); //"11000"

is 11010, not 11000.

Note from the Author or Editor:
Please change this line in the second example:

alert(result3.toString(2)); //"11000"

To this:

alert(result3.toString(2)); //"11010"

The sentence reads, "A property can be evaluated by placing its name between ${and }."

There should be a space between "${" and "and".

Note from the Author or Editor:
In the sentence, "A property can be evaluated by placing its name between ${and }.", add a space between "${" and "and".

The line:

for (i = 0; i < count; i++) {

is indented two spaces, but it should not have any indent.

Note from the Author or Editor:
The first instance of this line is currently indented in the example code:

for (i = 0; i < count; i++) {

There should be no indent ("for" should align at the first column)

In the following line, the second string literal contains an extra space:

alert('created ' + count + ' in ' +

presumably it should be:

' in '

Note from the Author or Editor:
On this line:

alert('created ' + count + ' in ' +

Please ensure there is only one space before and after the word "in".

Should be "Firebug" rather than "FireBug."

Note from the Author or Editor:
Please replace the word "FireBug" with "Firebug".

Extra space before the equals sign on this line:

element.className = 'foobar';

Note from the Author or Editor:
In the code, please ensure there is only one space between "element.className" and the equals sign in:

element.className = 'foobar';

Case in code sample does not match that of figure.

On page 190, the code is:

foo.displayName = 'I am foo';

but in the figure on 191, the name is:

'i am foo'

so the case of 'i' is inconsistent.

Presumably it is easier to update the code sample than the screenshot.

Note from the Author or Editor:
Please change this line in the last code sample:

foo.displayName = "I am foo";

To this:

foo.displayName = "i am foo";

Note that the word "displayName" should still be bold.

Inconsistent comma placement:

"Loading", "Scripting," or "Rendering".

For consistency, this should be one of the following:

"Loading", "Scripting", or "Rendering".
"Loading," "Scripting," or "Rendering."

Note from the Author or Editor:
Please change this:

"Loading", "Scripting," or "Rendering".

To this:

"Loading", "Scripting", or "Rendering".

The sentence reads, "...requests that a event may be triggering..."

"a event" should be "an event"

Note from the Author or Editor:
In the sentence containing, "...requests that a event may be triggering...", replace "a" with "an".