Web Programming Step by Step, by Marty Stepp, Jessica Miller, and Victoria Kirst

Errata for Second Edition

Many thanks to everyone who has submitted corrections! Your names will appear in the acknowledgements in future printings of the textbook.

(If you think you've found an error in our textbook, please email us!)

Unfixed Errors:

p55 (John Howard) - Table 3.3 lists the standord CSS color names. But it erroneously omits orange, which was added in CSS 2.1.
p64 (Robert Hieger, NYU Polytechnic School of Engineering) - The CSS text-decoration: blink; is becoming deprecated because it is not supported by most modern web browsers. This is because it was deemed annoying by web users.
p68 (Robert Hieger, NYU Polytechnic School of Engineering) - In code Example 3.30, the CSS includes a selector related to table captioning that is not W3C compliant. The CSS code reads:
```
table {
  caption-side: left;
  font: 14px "Comic Sans MS";
}
```
The caption-side property should not be set to left in W3C-compliant CSS code. The compliant values are top (default value), bottom, and inherit.
p126 (Claude Anderson, Rose-Hulman Institute of Technology) - In code Example 4.35, the following line of CSS code has a semicolon that should be a colon. The line:
```
  border; 2px solid black;
```
should be:
```
  border: 2px solid black;
```
p135 (Claude Anderson, Rose-Hulman Institute of Technology) - In the page's second paragraph, the line, "The page's desired appearance is shown in Figure 4.1." is technically correct, because Figure 4.1 does show the desired appearance for the Ultimate Frisbee page, but it would be more clear for the line to say, "The page's desired appearance is shown in Figure 4.17." since Figure 4.17 is a repeat of Figure 4.1 on that same page.
p168 (Claude Anderson, Rose-Hulman Institute of Technology) - Near the end of the page text, the phrase, "lead undesirable results" should be, "lead to undesirable results".
p193 (Estee Ratus) - The quadratic equation formula for Self-Check 5.15 should be:
p211 (Claude Anderson, Rose-Hulman Institute of Technology) - Near the top of the page text, the phrase, "required or match" should be, "required or must match".
p235 (Raphael Abberbock, Yeshiva University) - In the description of JavaScript array methods, we neglect to mention that the array sort() method always sorts the contents in their alphabetical (lexical) order, as though they were strings. This is often what you want, but it can produce confusing results when you have an array of numbers, because for example "10" comes before "2".
p316 (Dan Schuster, Western State Colorado University) - In the description of JavaScript array methods, we neglect to mention that the array sort() method always sorts the contents in their alphabetical (lexical) order, as though they were strings. This is often what you want, but it can produce confusing results when you have an array of numbers, because for example "10" comes before "2".
p349 (Jamil Saquer, Missouri State University) - Table 9.9 lists the textContent property as being supported by all browsers except IE. As of IE 9, Internet Explorer does now support the property.
p350 (Claude Anderson, Rose-Hulman Institute of Technology) - In the second-to-last paragraph on this page, the sentence, "Keeping the shuffling algorithm from the DOM and event code will help us keep the code cleaner and avoid bugs." should read, "Keeping the shuffling algorithm separate from the DOM and event code will help us keep the code cleaner and avoid bugs."
p390 (Erik Krohn, University of Wisconsin Oshkosh) - In the page's last paragraph, the sentence mistakenly says, "XX demonstrates this technique." It should say, "Example 10.12 demonstrates this technique."
p420 (Matt Schafer, University of the Pacific) - A line of code in Example 11.11 contains an extra closing parenthesis. The following line:
```
  var letter = String.fromCharCode(event.keyCode));
```
should be:
```
  var letter = String.fromCharCode(event.keyCode));
```
p534 (Michael Marvick, University of Washington) - In code Example 13.67, the following line:
```
$rows = perform_query($query);
```
should be:
```
$rows = perform_query($countries_query);
```
p624 (Jamil Saquer, Missouri State University) - In the table of HTML elements on this page, the last entry mistakenly claims that <hr /> is an inline element. It is not; it is a block element.

Fixed Errors:

The following errors are fixed in all 2nd edition copies ordered on or after July 25, 2012. Copies of the 2nd edition bought before that time still contain the errors below.

p.v (Richard Fuhr) - In the list of content revisions near the middle of the page, the following sentence has misspelled the word "HTML": "We introduce new tags such as audio, video, meter, and datalist, as well as many of the new ~~HTLM~~ HTML form controls and attributes."
p51 (Staci Menz, UW student) - The sentence, "In 1994-96 he W3C reviewed..." should read, "In 1994-96 the W3C reviewed..."
p100 (Robert Jacobson, UW student) - The description of borders at the bottom of the page implies that their width can be specified as a percentage (%). It cannot.
p221 (Staci Menz, UW student) - The sentence at the bottom of the page, "XX demonstrates a basic data list." should read, "Example 6.17 demonstrates a basic data list."
p288 (Staci Menz, UW student) - The sentence near the bottom of the page, "Suppose you want to the image's source URL to instead show an image of a dog stored in dog.jpg." should read, "Suppose you want the image's source URL to instead show an image of a dog stored in dog.jpg."
p291 (Staci Menz, UW student) - The sentence near the middle of the page, "After clicking the Compute button error message shows up in our Error Console stating that..." should read, "After clicking the Compute button, an error message shows up in our Error Console stating that..."
p295 (Staci Menz, UW student) - Near the middle of the page, there are some stray characters, "aoeu" on a line by themselves. These characters should not be there and should be ignored.
p307 (Rishi Agarwal, UW student) - At the end of the second paragraph, a sentence about == and != begins with "For example," and then stops abruptly without providing the examples. Here are the example expressions that should have been listed afterward:
- "" == "0" is false
- 0 == "" is true
- null == undefined is true
- " \t " == 0 is true
All of the above tests would produce false when used with ===. JavaScript guru Douglas Crockford calls == and != the "evil twins" of === and !== in his book, JavaScript: The Good Parts.
p367 (Rishi Agarwal, UW student) - The caption for Example 9.41 should read, "Example 9.41 Modifying a single element using ~~$$~~ document.querySelector".
p471 (Rishi Agarwal and Staci Menz, UW students) - The first paragraph, which begins, "The key difference with JSON ..." is mistakenly repeated again later in the page underneath Example 12.36. The second occurrence should be deleted.
p472 - In the page's last paragraph, the first sentence, "The code for processing such JSON data upon its return from the server is shown in XX." should read, "The code for processing such JSON data upon its return from the server is shown in Example 12.38."
p553 (Staci Menz, UW student) - The page's second-to-last sentence has an extraneous word: "... a large associative array, keyed by session IDs, that maintains of data about ..."
p568 (Staci Menz, UW student) - The word "page" is misspelled as "pag" near the middle of the page: "It would be nice if we could display a quick message whenever we do a redirection from one page to another, ..."
p570 (Staci Menz, UW student) - This sentence in the page's last paragraph has poor subject-verb agreement: "The file bottom.php and index.php are unchanged from its original version shown in Example 14.18, so it is not repeated here." The sentence should read, "The files bottom.php and index.php are unchanged from their original versions shown in Example 14.18, so they are not repeated here."

Errors in other supporting materials:

(Dr. Robert Moniot, Fordham College) The code samples in Ch. 9 lecture slides #31 and #32 contained minor code bugs. Slide 31 contained a superfluous document.getElementById call, and Slide 32 said remove where it should have said removeChild.

Reporting Errors:

Have you found an error in our textbook? If so, please email us at:

authors contact