Page 16: All references to “page breaks” on this page are actually referring to “line breaks.”
Page 62, Example 4-13, line 5: Missing first quote mark in what should be colspan="2".
Page 109, second paragraph of The Cascade: “... inline trumps embedded ... embedded takes precedence over inline ...” The first part is correct. That is, if you specify conflicting values for an attribute in both an embedded rule and an inline rule, the inline rule is the one that is used. The real problem here is that the cascade takes much more than one paragraph to cover accurately.
Page 113, line -4: “In this case, the media is defined as screen.” But Figure 7-3 uses media="all".
Page 120, line 6: “...can be represented by a single number or character...” should be “...can be represented by just two numbers or characters...” (Each hexadecimal digit represents 4 bits.)
Page 124, paragraph 4: “This is because there is no effective means of providing cellspacing in CSS.” True. But the box model (padding) should be used in place of cellpadding.
Page 124, Example 8-4: “th ... border:}” should be “th ... border: 1px solid black;}”
Page 124, Example 8-4: Note that the color orange doesn’t pass W3C validation yet; it’s part of CSS 2.1, not 2.0. But all current browsers support it.
Page 129, last paragraph: “...it simply strengthens the case that the property will be inherited by its decendents.” This statement is ambiguous as it stands. An attribute value of “inherit” means that the element inherits the property’s value from its parent. This is the normal case, so this value is seldom used.
Page 154, Figure 9-13: The callouts that have names starting “text-decoration” should all be “text-transform,” and the line going from the lowercase callout should go only as far as the by-line (“by edgar allen poe”), not all the way down to the word “With.”