the placeOrder function should take in the form object as a parameter in order for the form.submit() to
work.... same error as pages 73 and 74

CURRENT:
The key to accessing a web page element with JavaScript is the id attribute of the HTML tag.

REVISED:
The key to accessing a web page element with JavaScript is the id attribute of the input tag.

The sample code on page 73 and 74 won't work because the form in "form.submit()" does not have
a form object to work with. I think placeOrder should probably be getting the form object in as a
parameter.

example shows the property to get the height of the client window to be clientWindowHeight - it should
be clientHeight.

In the touchRock function, the operation of getting the userName first is missing.

function touchRock() {
userName = readCookie("irock_username");

[ Rest of code is correct ]
}

Under the second large paragraph with the seat# functions, <img id="seat14" src=" alt="" /> is missing a quotation mark under src=. It should be <img id="seat14" src="" alt="" /> instead.

I'm not sure if you would consider this a mistake. I think that I read in the XHTML Head First
that there should probably be a space between the /> and everything preceding it in an empty tag. Like
this:

<br/> to <br />

just to accommodate older browsers.

On page 300-302, the code

<input id="phone" name="phone" type="text" size="12" onblur="validateNonEmpty(this);"/>

there is no such space.

Perhaps I am misunderstanding this, but on page 309 it says

"The purpose of this.form in the Bannerocity code is to gain access to the help text element that is
associated with a particular input field. Remember that this.form is a reference...."

I understand the concept presented here but I don't see it being used, which confuses me as to why
the text above implies that it is being used.

If this method comes up in later pages, why not put this question after it comes up in the book?
To me, it seems like it might confuse a reader who has never seen this before since it hasn't even
been used in the book yet.

What is being used is a document.getElementById('help_text_name') instead of a
this.form["help_text"]....
especially since the book mentions that the form approach is more concise but it doesn't seem to be
using it?

You give 2 examples of character classes, one is /d[iu]g/ and the other is /$d[d.]/ . Shouldn't that
second example be /$d[.d]/? The difference is between the brackets.

On page 338, the answer key shows the answer is return
validateRegEx ( /^[w.-_/+]+@[w_]+(.w{2,4})+$/..... but shouldn't it be
validateRegEx (/^[w.-_/+]+@[w_]+[.w{2,4}]+$/..... (using brackets instead
of parentheses for testing the domain suffix) ?

font-color should just be color. font-color is not a valid css property.

I think the second code sample should actually be this:
decisionElem.appendChild(document.createTextNode("Decision 1 -> Scene 1: Fork in the road."));
it is currently missing the createTextNode portion.

I think this line on page 384 of H.F. java script:
decisionElem.appendChild("Decision 1 -> Scene 1 : Fork in the road."));

should be:
decisionElem.appendChild(document.createTextNode("Decision 1 -> Scene 1 : Fork in the road."));

The line in the book throws a "type mismatch" error.

The ceiling function doesn't work in either Firefox or IE. Is it in this version of the standard?

I think that's not correct that 'undefined' and 'not defined' mean exactly the same thing.

'not defined' means, that the variable does not exists/has not been created.

'undefined' means an undefined state, the variable exists/has been created but it's not initialized (no value has been assigned to the variable)

example for undefined:
<code>
var testVariable;
alert(testVariable);
</code>
the result is an alert-box with message-text 'undefined'

example for not defined:
<code>
alert(testVariable);
</code>
the result is a message in the error console:'testVariable is not defined'