HTML & CSS: The Good Parts

Errata for HTML & CSS: The Good Parts

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page xxi
5th graf after "What's Not In This Book" -- "Integration w/ frameworks..."

Accuracy: the question of framework deployment is raised briefly (without endorsement) in Chapter 5.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page xxiii
xxiii, 5th graf

Accuracy: validators do count as an objective enforcement mechanism, to a point. This language should be softened.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page xxv
2nd full graf

Accuracy: Sun was bought by Oracle Corp. while the book was being written, which change didn't make it into the copy in time.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page xxvi
1st graf

Jarring omission: the title "stylist" gets a lot of play in the book, but this paragraph was never edited to reflect that evolution.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page xxix
Acks, 7th graf

Doug Petersen's name is misspelled, it should be "Peterson"

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 2
1st graf of section headed "URIs", 2nd sentence

Accuracy: change "but isn't" too "but often isn't"

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 9
Figure 2-1

The final passage in the left column is a trainwreck: change to "the closing tags will rest in the /reverse/ order of their opening counterparts."

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 14
4th graf (after list of universal attrs)

Accuracy: the style element is also primed for abuse in Chapter 3.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 16
Second footprint note

"... they should be attached to the html element, instead of the html element." One of these "html" instances should be something else.

Note from the Author or Editor:
Change second instance of "html" in this passage to "body"

Porter Scobey  Apr 16, 2010 
Printed
Page 16
2nd callout

"the the" at beginning of callout needs repair

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 19
Example 2-2

The nesting of child tags should be increased for the sake of legibility.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 20
callout

Transparency: The callout should be edited to *further* emphasize that the id nomenclature displayed is the author's, not necessarily a nomenclature that is in common use

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 21
final full graf, last sentence

"asynchronously" before "request and insert" should be emphasized, by way of underscoring its status as the "A" in "Ajax".

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 24
IE conditional stylesheet call example

Clarity: Example currently reads "if IE lt 8" when (given the matter raised in the preceding callout) "if IE lt 7" might make more sense.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 24
final graf

Accuracy: The * html low pass filter is briefly explained in Chapter 14 and the underscore hack is similarly treated in Chapter 4, but low pass filters are not given their own dedicated passage in the book as was originally intended when this paragraph was written.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 25
Final graf of "Using @import"

"called @import" should read "called via @import"

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 27
1st item on page

Typo: insert "to" after "applicable" (i.e., "applicable TO mobile device displays")

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 28
Line 6, starting with "nesting opens to ... "

Should be: "nesting opens the"

Porter Scobey  Apr 16, 2010 
Printed
Page 28
First line of last paragraph, starting with, "CSS makes a ..."

The word "made" should be removed.

Note from the Author or Editor:
The reader's suggestion is excellent.

Porter Scobey  Apr 16, 2010 
Printed
Page 28
Definition list of document tree related terms

Text nodes would ideally be mentioned in here somewhere.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 28
final graf

"made" in "makes a clear distinction made" is superfluous

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 30
Table 3-1

Throughout the book selectors and property names are arbitrarily broken between lines, but this formatting convention is NEVER skylined ANYWHERE in the book.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 31
Precedence list below "Selector Priority" intro

Change the example "first-letter" in item 4 to ":before, :after". Change "[selected="selected"]" in item 5 to "[type="text"]".

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 33
1st graf

The final sentence ("The latter element...") should in fact be joined to its predecessor in order to keep the paragraph from being a trainwreck, but ideally that entire paragraph would be rewritten - it runs on.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
PDF
Page 33
Table 3-2. Commonly encountered CSS length/size, keyword, and color units

There is an semicolon between the property and value on the 2nd line of the table instead of a colon: "margin-left; 1.25em;"

Note from the Author or Editor:
[orrect as supplied]

shonket  May 23, 2010 
Printed
Page 36
2nd graf

"With greater ease" reads poorly; replace with "more easily"

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 37
List of color notation styles

There is no consistency or transparency with respect to the treatment of NAMED colors in the book, though they do make a few cameos.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 38
Table 3-5

It's impossible to pick out the default values from the second column! (Additionally: bullets?!)

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Printed
Page 40
Figure 3-2

Outlines of the various elements pictured should be broken at intersections, to illuminate the stacking order of the named elements. The selectors alone can be used to deduce the stacking order, but leaving that to the intended readers of this book is really unfair, especially since stacking order isn't at all raised explicitly for another three chapters.

Ben Henick
O'Reilly Author 
Apr 17, 2010 
Other Digital Version
52
Second Paragraph after "Providing Stylesheet Hooks with class and id" heading

"class and id values... ...should begin only with numbers and letters". In HTML 4, Id's should begin only with letters: http://www.w3.org/TR/html4/types.html#type-id Looks like that is changing for HTML 5: http://dev.w3.org/html5/spec/elements.html#the-id-attribute

Note from the Author or Editor:
"Minor" only because browsers will still browse such values properly in spite of the expectations posed by the spec.

Charles Overbeck  May 25, 2010 
Printed
Page 271
Third paragraph of section "Issues with XHTML and XML"

The text says "you're begging for trouble if you serve your documents as text/xhtml+xml". This is true, as this MIME type does not exist. I think the author meant "application/xhtml+xml" instead of "text/xhtml+xml".

Note from the Author or Editor:
The reader's suggestion is absolutely correct.

Gregor Zurowski  Mar 31, 2010