: important language/formatting problem
(page-number): language change or minor formatting problem
?page-number?: reader question or request for clarification
This errata page lists errors *corrected* in the 5/08 reprint.
(17) Figure 2-1;
The figure is missing an exclamation point at the end of the line that reads: Hello, World Wide Web
(32) Figure 2-5, 3rd paragraph;
"wiht" should be "with"
(32) line 5
"for multicolumn text and" should be removed
[43] Section 3.5.3 on comments;
The statement "There must be a space after the initial " is not correct. There is no
such requirement in either HTML nor XML according to the w3c documents referenced below.
However, there is a restriction on the content of a comment that is not mentioned in the book: Two adjacent hyphens may
not appear in the body of a comment. This is a strange restriction since --> is
the terminator and -- followed by something other than > should not be that hard for a parser to deal with.
Even stranger, the HTML doc says that whitespace may appear between the -- and the > terminating the comment. So , but
otherwise you can put nearly anything inside the comment.”
with:
“You can put nearly anything you’d like inside a comment.”
(52) section 3.8.2, line 4
Replace "this innovation" with "Frames".
(53) footnote
Replace "know" with "known"
(54) line 5
Change "2003" -> "2007"
(61) box for
Add "onClick" to list of attributes
(98) line before the box
Change "in Figure 4-20" -> "in Figure 4-19"
{176} The gopher path
The example line should be 3 lines, each line starting "type/..."
{180} code above screenshot, line 2
Change "status" -> "self.status"
(217) cross references at end of section 7.2.1.4
Dir is 3.6.1.1, lang is 3.6.1.2, id is 4.1.1.4 and title is
4.1.1.5.
(220) cross references at end of section 7.3.1.4
same as for page 217
See previous answer for dir, lang, id and title attribute assignments.
{226} 7.5.3.1 first paragraph;
This paragraph is a copy of the paragraph in section 7.5.2.2. But the HTML tag that it is describing should be changed
from
to .
Author reply:
We're changing “” to “” in this paragraph.
(233) last line
"The id attribute" -> "The title attribute"
"4.1.1.4" -> "4.1.1.5"
{243} last line before heading 8.2.6
Note: With version 7, Internet Explorer now supports attribute selectors.
(273) all 3 figures
These 3 figures should show the rendering of the value "bottom" (instead of "text-bottom").
{283} 5th paragraph (4th complete paragraph);
Section 8.4.7.13 on the Overflow Property states that "none of the currently popular browsers supports the overflow
property"
This would seem to be outdated information, perhaps left from an earlier addition?
Safari, Firefox, IE 6 (with some issues) and IE 7 all support overflow.
http://www.w3schools.com/css/css_positioning.asp
Author reply"
The URL given allows me to test and confirm that this is supported in IE and Firefox. We're removing that sentence.
(284) line 5 from bottom
Change "Figure 8-8" -> "Figure 8-14"
(287) 8.4.8.3
End of first paragraph: The cross-reference should refer to 7.2.1.2
[321] 4th paragraph;
The book says:
You can use a mailto URL as the value of the form's action attribute. The latest browsers automatically email the
various form parameters and values to the address supplied in the URL.
I tried the following form (with the right email address) and my IE 6.0 brings up my email client - the browser doesn't
email the form.
The issue is also described and discussed at -
http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=20&t=008553
Author reply:
Here an email is composed for you, but the user must actually click the send button to send it. This is a deviation
from early browsers, which silently sent the message on your behalf.
In any case, the sentence: “The latest browsers automatically email the various form parameters and values to the
address supplied in the URL.”
will be replaced by:
“Older browserswill silently email the various form parameters and values to the address supplied in the URL. For
security purposes, the latest browsers will instead use the default messaging client to compose the email, relying upon
the user to click the “Send” button to transmit the message.”.
[337] 9.7.1.2;
The text of this section refer to 'virtual' and 'physical' as valid values for the wrap attribute. 'soft' and 'hard'
should be used instead.
Author reply:
True enough. Netscape 3.0 tried to make the virtual/physical values a standard but gave up. All occurrences
of “physical” will be replaced by “hard” in this section, and all occurrences of “virtual” with “soft.” In addition,
the following paragraph will be included at the very end of the section:
Note that early versions of the Netscape browser used virtual and physical in place of soft and hard for this
attribute. These values are generally not supported today; we mention them here only to provide clarity should you
stumble across some ancient bit of HTML in your web wanderings.
[344]
Setting the tabIndex to 0 does not always exclude the element from the
tabbing order. In my IE version 6.0 setting tabIndex to -1 works fine, though.
Author reply:
This is true. Positive integers create a tab order, -1 removes an element from the tab order, and 0 leaves the item in
the order after numbered items, in the order declared in the file.
This paragraph will be replaced:
The value of the tabindex attribute is a positive integer indicating the position of the tagged contents in the overall
tab sequence for the document. The tabbing order begins with elements with explicit tabindex values, starting from the
lowest to the highest numbers. Same-valued tags get tab-selected in the order in which they appear in the document. All
other selectable tags, such as the various form controls and hyperlinks, are the last to get tabbed, in the order in
which they appear in the document. To exclude an element from the tab order, set the value of tabindex to 0. The
element is skipped when the user tabs around the form.
with this:
The value of the tabindex attribute is a positive integer indicating the position of the tagged contents in the overall
tab sequence for the document. The tabbing order begins with elements with explicit tabindex values greater than zero,
starting from the lowest to the highest numbers. Same-valued tags get tab-selected in the order in which they appear in
the document. All other selectable tags, including those with tabindex set to 0, then get tabbed in the order in which
they appear in the document. To exclude an element from the tab order, set the value of tabindex to -1. The element is
skipped when the user tabs around the form. Finally, in the next paragraph, replace “while notab is equivalent to
tabindex=0” with “while notab is equivalent to tabindex=-1”.
(370) 2nd line below figure 10-3
The cross-reference to section 10.2.3.1 is a self-reference (this is section 10.2.3.1). It should be a reference to
10.2.4.1.
(382) end of 1st paragraph in 10.3.5
The cross-reference should point to 10.2.1.4
(400) 2nd line
The cross-reference should point to 11.4.1.2.
(420) 4th line
The cross-reference should point to section 12.2.1.6.
(463) last line
"" should be replaced by "" (and "" removed from the first line on page 464)
{498} Section 16.2.3;
The given xmlns element is wrong, and appears to be derived from the DOCTYPE element. It is rejected by the W3C
validation software version 0.8.2.
http://validator.w3.org/
You have
But the "TR" should be "1999"
And the "xhtml1" should not have the '1': "xhtml" is correct
These appear twice near the end of section 16.2
Author reply:
Correct. Both occurrences of “/TR/xhtml1” will be replaced with “/1999/xhtml” in this section.