Errata for Head First HTML with CSS & XHTML

add "the" in front of "container" ("...of the width of the container the element is in...")

Screen shot on p448 does not reflect "margin-left: 20px;" given on p447.

The clue says "list-item-position can be used..." it should be "list-style-position"

Note from the Author or Editor:
Also, error on page 580 where we say "line"-style-position instead of "list"-style-position

says "there's no green badge of success when you pass validation like there is when you validate XHTML..." But now there is. Also, the latest validator doesn't show the warnings in your screenshot

Note from the Author or Editor:
Need to update screenshots for 2nd ed.

Update needed: You say “It’s likely there won’t be an HTML 5….”

Note from the Author or Editor:
Update for 2nd ed

The table's Temp column contains data with the degree-symbol while the content in the XHTML later on does not; throughout the rest of chapter 13 the degree-symbol appears and disappears.

Note from the Author or Editor:
Fix to not use degree symbol or show how to do it with entity.

Bountiful's Altitude reads "4,.226 ft" rather than "4,226 ft"

"Hex codes have 6 digits, and each digit can be from 0-F." I believe they mean that Hex codes can have 16 digits.

Note from the Author or Editor:
no actually here we're talking about css colors, which have 6. But it's not clear.

"but there's a few more elements ..." should be "but there're (or there are) a few more elements ..."

Under Eric's information the last full paragraph has a sentence that reads "When he's not writing text or code you'll find him spending more time tweaking than watching his home theater and trying to restoring a circa 1980s Dragon's Lair video game." It should read "restore" not "restoring."

At the end of the line of code, to adhere to strict XHTML, the method="GET" should be method="get". The annotation pointing to this should therefore be changed to: "Just change the method from "post" to "get"."

Note from the Author or Editor:
Technically this is true, and should probably be changed throughout this chapter on the next edition. (GET/POST appear in multiple places throughout this chapter). I don't think it's worth changing for a print edition, however.

In the checkbox input box, the example displayed shows capitalized checkbox values (Salt, Pepper, Garlic), while the HTML code have non-capitalized values (value="salt", value="pepper", value="garlic"). These should be one or the other and agree.

Note from the Author or Editor:
Confirmed. The values in the <input...> lines should be updated to show uppercase first letters. I noticed another errata on page 598; in the text input line, <input type="text" name="fullname", this needs a /> added to the end of this line. NOTE: this has been corrected in the January 2009 printing.

The first question in Dumb Questions reads: "So why did you make the sector #guarantee rather than p#guarantee? I believe "sector" should actually be "selector". Best Regards and thanks for some great books. I've got 'em all either hardcopy or safari infomit. I don't think there are any pdf's available yet! Michael Canfield

Note from the Author or Editor:
Confirmed. sector should be changed to selector

I'm just confirming that the file that we are instructed to open to do this exercise (lounge.html) is incorrect, and that it should have been printed with "elixir.html". Someone else has already submitted this error, but I'm confirming that lounge.html does not include any info regarding class details as we were instructed to change. Thanks.

Note from the Author or Editor:
Confirmed. lounge.html should be changed to elixir.html

"We're going put" should be "We're going to put"

In the description of Chai Chiller, "mate&eacute;" should be "maté" (an "e" with an acute accent)

complaint HTML or XTHML should be compliant

At the end of the third phrase on the 6th paragraph: "For example, studies show .... causes your brain to try to makes sense of ...." Should be: "For example, studies show .... causes your brain to try to make sense of ...."

"HTML" & "CSS" Fireside Chat column headings are missing on page 35.

Bullet Points, 7th bullet left column; The sentence is: "Opening tags can have attributes. We've seen a couple: type and align". However, the "align" attribute can be found nowhere in the previous pages.

6 Down should have 9 spaces, not 8 (it's "50sKitsch," not "50sKitch").

Continue on Stucture Ave S - go 0.2 mi should be: Continue on Structure Ave S - go 0.2 mi

Continue on Stucture Ave S - go 0.2 mi should be: Continue on Structure Ave S - go 0.2 m

The clue for 8 Down should read, "The 'HT' in HTML," (not "The 'H' in HTML")

The 2nd sentence in the 1st paragraph reads: "You'll find it in his July 14th entry." The sentence should read: "You'll find it in his June 2nd entry."

The sentence reads, "So, while you can probably count on the basic entities from the www.w3schools.com to be available..." It should read "...from the www.w3schools.com *page* to be available..."

Change "getting an hosting company" to "getting a hosting company".

Change "you're going need your own domain name" to "you're going to need your own domain name"

As with finding an hosting... should be As with finding a hosting...

The W3C web page has changed and your pic is out of date.

Note from the Author or Editor:
Yup, we'll be updating this soon.

Change "...is going to be a fast for you." to "...is going to be fast for you."

The sentence, "All attribute values must be surrounded by double quotes and must have values." It sounds like you're saying that, in addition to being surrounded by double quotes, "All attribute values must have values." A bit tautalogical, eh? It should read something like, "All attributes must have values, and those values must be surrounded by double quotes."

"On the next page .... that we're going create by the end...." should be "On the next page .... that we're going to create by the end...."

Le Roi..., *Engima* should be Le Roi..., *Enigma*.

"So why did you make the sector" should be "So why did you make the selector"

"it is also shows" should be "it also shows"

Change "...you can use a just a number instead..." to "...you can use just a number instead..."

The 2nd paragraph reads: "Now let's add some style. Add these two rules to the bottom of your "lounge.html" file:" This sentence should read: "Now let's add some style. Add these two rules to the bottom of your "lounge.css" file:"

Change "Give it try!" to "Give it a try!"

"readers" should be "reader's"

"figure out how display" should be "figure out how to display"

"Move the entire ..... to top the of the file ....." should be "Move the entire ..... to the top of the file ....."

"Try your hand at calculating these the specificity of these selectors..." should read: "Try your hand at calculating the specificity of these selectors.."

The "Exercise" begins "Move the elixirs <div> back to its original place below the music recommendations..." The original position of the the elixirs <div> was *above* the music recommendations.

Note from the Author or Editor:
Will be fixed in 2nd ed

Annotations point at the wrong sections of code. Second arrow from bottom should point to "h1" section, and bottom arrow should point to ".slogan" line.

The "Be the Browser" solution (on page 544, original exercise on p 490) shows both <div> elements at the bottom of the page. But, at the end of chapter 11, as part of the "Super Brain Power" exercise, the "elixirs" <div> was moved to the top of the page, just under the <p> containing the Head First Lounge logo. So, the correct order in the solution should actually be: <p> <div> <h1> <p> <p> <p> <p> <p> <h2> <p> <ul> <div>

Note from the Author or Editor:
Fixed in 2nd ed

The <title> definition in the sample code (including the downloaded sample) defines the title as "Testing Tony's Table" but the title on the browser graphic is "Testing Tony's Travels".... one or the other should be changed.

Handwriting-style comment talks about ending the element with " />", but the actual " />" does not appear in the HTML element shown. As a result, there's an arrow pointing at something that isn't there...

"Didn't you say that the names for each form element needs to be unique?" doesn't sound right Change to "Didn't you say that the name for each form element needs to be unique?" instead?

"Also notice that the we've used" should be "Also notice that we've used"

"Instead of a .... you'll get a the multiple choice..." should be "Instead of a .... you'll get a multiple choice..."