The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Version |
Location |
Description |
Submitted by |
Date submitted |
Printed |
Page xii
first line of page |
should say "Anywhere from one to four..." and not "...zero to four..."
|
Anonymous |
|
Printed |
Page xii
first line of page |
A previous reader's comment:
should say "Anywhere from one to four..." and not "...zero to four..."
is not quite true. There is a contradiction in the use of the conventions: the
brackets indicate that the word "really" must be repeated at least once but
not more than four times. However, the asterisk after the brackets indicate
that the preceding value (i.e., really) can be used any number of times --
including zero.
|
Anonymous |
|
Printed |
Page back cover
|
Dynamic HTML: The Definitive Guide" should be Dynamic HTML: The Definitive Reference.
|
Anonymous |
|
Printed |
Page 15
Section "The @import directive" |
the urls for the @import statement throughout the book are not within quotation marks
and must be for the statement to work. Thus, on this page:
@import url(styles.9781565926226);
should be
@import url("styles.9781565926226");
@import url(sheet2.9781565926226);
should be
@import url("sheet2.9781565926226");
@import url(blueworld.9781565926226);
should be
@import url("blueworld.9781565926226");
@import url(zany.9781565926226);
should be
@import url("zany.9781565926226");
|
Anonymous |
|
Printed |
Page 16
Fig.1 and code in last para |
the urls for the @import statement throughout the book are not within quotation marks
and must be for the statement to work. Thus, on this page in both of the above
positions:
@import url(sheet2.9781565926226);
should be
@import url("sheet2.9781565926226");
|
Anonymous |
|
Printed |
Page 33
|
"octothorpe"
should be
"octothorp"
according to:
http://www.webster.com/cgi-bin/dictionary?va=octothorp
|
Anonymous |
|
Printed |
Page 35
2nd paragraph |
The description of unique ids independent of an element implies that the
author has previously defined an id in terms of an element, which is not the
case and is confusing.
|
Anonymous |
|
Printed |
Page 37
top section |
generic class reads
.delicate {font-weight; lighter;}
should be
.delicate {font-weight: lighter;}
(Semicolon after font-weight should be a colon)
|
Anonymous |
|
Printed |
Page 43
2nd para |
"In figure 2-18, the first UL element is parent to two LI elements and a UL"
Surely, the first UL is ancestor to the second UL, not parent? A LI is the parent to
the second UL and the first UL is that LI's parent.
|
Anonymous |
|
Printed |
Page 63
2nd paragraph of "Reproducing Colors" section |
The last sentence of the paragraph says "...graphics created on Windows machines tend
to appear darker to Macintosh users, whereas images created on a Macintosh look
lighter for Windows users."
The actual situation is the exact reverse of that. Graphics created on Windows
machines tend to appear LIGHTER to Macintosh users, whereas images created on a
Macintosh look DARKER for Windows users.
|
Anonymous |
|
Printed |
Page 67
3rd paragraph |
In the example:
p.one {color: rgb(300,2500,101);} /* white */
shouldn't the third rgb value be 255 or greater?
|
Anonymous |
|
Printed |
Page 70
Table 3-4, "Color Equivalents" |
The color Green is shown with the same equivlents as the color Lime. It should
read Green rgb(0%,50%,0%) rgb(0,128,0) #008000.
|
Anonymous |
|
Printed |
Page 71
Table 3-4, "Color Equivalents" (continued) |
Fuchsia is shown as "fuschia."
|
Anonymous |
|
Printed |
Page 73
1st paragraph |
The description of points is emphatically wrong in several regards.
First, the minor wrong issue: _Postscript_ points, by definition, are 72 to an inch.
That works for desktop publishing, but is a simplification of the original American
definition, still used by most printers, of 72.17something per inch (points and picas
originally had no relation to inches, obviously). It would be awful to get deeply
into this issue, but it is important to note points, as defined in Postscript, vs.
points, the American printer measure, just in case. American printer points (which
are different from the original British--but they use our system now, and French--who
now call their unit "didot") preceded more than metric ;-).
But the big issue is how points relate to type.
1. There is no defined necessary relation between point size and physical size of
type shapes. Historically and currently, a designer of a typeface is free to design a
typeface that is any size. In other words, the distance from ascender to descender
might commonly be equal to the point size (and would traditionally be defined as
approximately that, based on the metal body behind the type), but there is no
obligation to design that way, and for display purposes, designers often don't.
They're encouraged to do, but they don't.
In all events, it would be unusual and extraordinary that an 18pt "P", as noted here,
were physically 18pts tall. In the usual circumstance, figuring that about 2/3 of the
pt size were distributed from baseline to ascender (1/3 reserved for descenders,
which, except for the tail of a swash "Q", don't occur with upper case letters), and
realizing that cap height is usually a hair less than ascender height (a common
adjustment for visual stuff), then one might except an 18pt "P" to be about 11 pts
high.
How different are the physical sizes of type characters, and by how much does x-
height vary? The easiest way to see this is to print characters in Helvetica (or the
modern computer analogue, Arial) next to the equivalent in Times Roman. (Or one can
look at the chart on p. 76.) Not only will the proportion of pt. size to cap height
to x height be difference internally, but the two fonts differ in their heights
relative to each other. (Because they are so different, of course, no visually
literate designer would use both fonts in one manuscript, even though the temptation
is there because they often comprise the entire type palette available on a given
computer.)
So, I'm not sure how to reword this, but it is very important to drive home the point
that the height of a character is usually roughly one third of the point size, which
is roughly equivalent also to cap height.
|
Anonymous |
|
Printed |
Page 75
3rd paragraph |
In the example:
<H2>Left margin = 18 pixels</H1>
shouldn't the closing HTML tag be </H2>?
|
Anonymous |
|
Printed |
Page 85
Figure 4-6 |
The text "Dia" from "Dia"mond Warehouse, Incorporated is on the top of the
image. From reading the book, I can't seem to find out how to keep the text
from being hidden underneath the image.
|
Anonymous |
|
Printed |
Page 88
2nd and 3rd paragraphs |
The book states that the style "text-align: center" is just like the <center>
tag, but <center> and <div align="center"> both center entire tables, but
"text-align: center" centers the text within the table cells instead.
The way to get the effect of the <center> tag is described on page 269:
margin-left: auto; margin-right: auto;
|
Anonymous |
|
Printed |
Page 126
last line (code entry) |
we can see rule P.signature {Author99, ScriptTM, serif;}
and this rule won't work, because in the declaration there is just value,
without specified property. There should be P.signature {font-family:
Author99, ScriptTM, serif;}
|
Anonymous |
|
Printed |
Page 202
the height syntax chart reads |
Values <length> | auto
It should read:
Values <length> | <percentage> | auto
|
Anonymous |
|
Printed |
Page 237
first paragraph |
Fig.7-58 shows an example of the rule H2{padding: 0.5em 2em; background silver;}. The
padding values are supposed to replicate to the bottom and left sides. Fig.7-58 does
not show H2 having a value of 2em for the left padding. Am I missing something?
|
Anonymous |
|
Printed |
Page 238
|
the code example doesn't work in IE 6 nor in Opera.
The rendering is frighteningly different in the (above) browser; but in
neither does it render as it does in the book (side by side paragraphs).
Both browsers render the div sections sequentially but vertically rather
than horizontally.
|
Anonymous |
|
Printed |
Page 271
3rd paragraph |
The second paragraph states "...the total of the 7 horizontal properties always
equals the WIDTH of the parent element." Fig. 8-19 illustrates an example of a
paragraph with a negative MARGIN-RIGHT number that is contained within a DIV having a
WIDTH of 400. The 7 horizontal properties of the paragraph add up to 410 pixels. The
third paragraph states that "Even though this leads to a child element sticking out
of its parent, technically the specification hasn't been violated, because the values
of the seven properties add up to the required total. ???? The width of the parent is
400 pixels and the width of the child is 410 pixels.
|
Anonymous |
|
Printed |
Page 273
example code at top of page |
<P CLASSS="neg">
should read
<P CLASS-"neg">
(one S too many)
|
Anonymous |
|
Printed |
Page 274
2nd paragraph |
Thus, there are only two pixels between the bottom
of the list item's content and the top of the
paragraph's content.
"paragraph's" should be "heading's".
|
Anonymous |
|
Printed |
Page 307
Property box, at top. |
The box and the subsequent text on page 308 and later in the chapter mention the
value "static-position". This value does not exist in the CSS2 or CSS2.1
specifications.
References: http://www.w3.org/TR/CSS21/visuren.html#position-props
http://www.w3.org/TR/CSS2/visuren.html#position-props
My copy is a May 2000 printing, but I did not see this error corrected in any
subsequent printing. No doubt you have not addressed this error because it will
require a substantial edit of chapter 9, but at least it should be documented here so
that people don't try to use this technique.
|
Anonymous |
|
Printed |
Page 329
3rd paragraph, first sentence |
... the positioned text overlaps the some of the content.
The 1st "the" should be omitted.
|
Anonymous |
|
Printed |
Page 332
1st paragraph |
The example is not valid for HTML 4.01 because a paragraph
can not be a child of another paragraph. Use instead <div>
|
Anonymous |
|
Printed |
Page 361
5th paragraph (last paragraph on page) |
The second sentence reads:
CSS2 adds a even more border properties, ...
It should be:
CSS2 adds even more border properties, ...
|
Anonymous |
|
Printed |
Page 387
Second block of code |
the urls for the @import directive throughout the book are not within quotation marks
and must be for the statement to work. Thus, on this page:
@import url(import-styles.9781565926226);
should be
@import url("import-styles.9781565926226");
|
Anonymous |
|
Printed |
Page 398
Top - link for Agitprop |
The link appears to have changed from
http://www.metrius.com/agitprop/
to
http://style.cleverchimp.com/
|
Anonymous |
|
Printed |
Page 416
list-style description, 2nd sentence |
in the text "elements with a display value of list-item", the word "display" should
be rendered in a monospaced font, as it is in the other list-style-x descriptions and
elsewhere in the book
|
Anonymous |
|
Printed |
Page 416
list-style-position description, Example |
the list-style-position Example reads:
LI {list-style-position: outer;}
but should be:
LI {list-style-position: outside;}
|
Anonymous |
|
Printed |
Page 422
Definition of "text-indent" property |
Second sentence of paragraph currently reads: This is most often used to create a tab
effect for Negative values are permitted, and cause "hanging indents."
Apparently, a word (or clause) has been omitted after "tab effect for".
Suggest: "indenting a paragraph's first line."
|
Anonymous |
|
Printed |
Page 446
|
I can't find a listing for HR (horizontal rule tag) in the index. I want to know if I can style HR tags using CSS but can't find out where or if this
is referenced in the book since it's not listed in the index or in the table
of contents.
|
Anonymous |
|
Printed |
Page 450
Absent |
The SPAN element does not appear in the index. This would appear to be related
to the fact that it is never formally introduced or described. At least I
can't find it. This would seem to be a major defect in an otherwise good book.
|
Anonymous |
|