Errata

Under the PC column resolutions are listed as:

640 x 480
800 x 600 (common on laptops)
1024 x 870
1280 x 1024
1600 x 1200

should be:

640 x 480
800 x 600 (common on laptops)
1024 x 768 <--
1152 x 870 <--
1280 x 1024
1600 x 1200

The monitor resolution 1152x870 is mentioned five times (six if you include
the typo in the PC column in Table 2-1). This resolution should be 1152x864
instead.

The HTML skeleton code is missing the <!DOCTYPE> tag. This tag is required if
the HTML is to be validated, as suggested on page 11.

The websafe color for lawngreen should be 66FF00. The websafe color for
lightpink should be FFCCCC. Either the RGB or hex color for tomato is
incorrect.

The first paragraph of the Summary of Structural Tags mentions "Browsers that
deprecate the tag". To my knowledge, and also according to the definition of
"deprecated" given on page 529, only a standard can deprecate a feature.

The "HTML 4D" notation on the <basefont> tag indicates that <basefont> is part
of HTML 4 but is deprecated. But the statement that "This tag is not part of
the HTML standard" indicates that <basefont> is not part of HTML 4. Is it or
isn't it?

<big> is not equivalent to <font size="+1"> unless the current font size is
the basefont size.

The description for the <small> tag indicates that IE 2 supports it but IE 3
does not. I think that IE support for <small> is the same as IE support for
<big>: supported by IE 3 but not IE 2.

For the REL and REV elements, HTML 4.01 specification does not recognize the
attribute values head, toc, parent, child. To use these it is necessary to
cite them as conventions with a profile attribute inside the HEAD tags.

Recognized attribute values for REL and REV not given here include alternate,
stylesheet, start, contents, copyright, chapter, section, subsection, appendix
help, bookmark.

reference:
http://www.w3.org/TR/html4/types.html#type-links

There is an extra ">" in the 2nd line and a "#" is missing from Line E. It
should be:

<IMG SRC="orbit.gif WIDTH=500 HEIGHT=125 BORDER=0 USEMAP="#spacey">

The usemap attribute of img must say USEMAP="#spacey" instead of
USEMAP="spacey".

The <object> tag is not supported by Netscape.

The page number given refers to the first edition, although the error
also appears in the second edition.

In the html shown 'NORESIZE' has been placed as an attribute of
the FRAMESET tag. This is incorrect. NORESIZE is an attribute
of FRAME.

In this particular example 'NORESIZE' should have been placed
in the <FRAME SRC="pix.html> because if this frame is prevented
from being resized none of the surrounding frames can be either.

The same error occurs also on page 224, 'Preloading Images with Hidden Frames' and on
page 225 'Getting Rid of Page Margins'

"The value multi-part/form-data should be used in
combination with the file input element."

"multipart/form-data" should not have a hyphen. With the extra hyphen, a Web
page using this enctype won't work properly (to be specific, file uploads via
the <INPUT TYPE="file"> tag won't work).

"When using the file input type, you should specify
enctype="multi-part/form-data" in the <form> tag..."

"multipart/form-data" should not have a hyphen. With the extra hyphen, a Web
page using this enctype won't work properly (to be specific, file uploads via
the <INPUT TYPE="file"> tag won't work).

For the Password Entry row, the example in the left-hand column is:

<INPUT type="file">

but should be

<INPUT type="password">

Javascript, you use the property "resize." It is actually "resizable."

The "font-face" value should be "font-family".

It states:

Note: CLASS names cannot contain spaces; use hyphens
or underscores instead if neccessary.

According the the CSS spec, the underscore is not a valid character. Silly, I
know, but here's the specific bit from the CSS1 spec:

in CSS1, selectors (element names, classes and IDs)
can contain only the characters A-Z, 0-9, and Unicode
characters 161-255, plus dash (-); they cannot start
with a dash or a digit; they can also contain escaped
characters and any Unicode character as a numeric code

It's in section 7.1, near the end
(http://www.w3.org/TR/REC-CSS1#forward-compatible-parsing).

Relying on your book's advice, I have happily used underscores, but have now
found that Netscape 6 follows the CSS spec so closely that this obscure rule
caused me a few hours of troubleshooting.

now reads:

Omit the HTML tag name to apply properties to all elements
with a given ID.

should read:

Omit the HTML tag name to apply properties to the element
with a given ID. Indeed there should be only one element
with a given ID.

cf. http://www.w3.org/TR/REC-html40/struct/global.html#adef-class

OL { list-style-type: upper-roman } (A., B., C., D., etc.)

Shouldn't "upper-roman" be "upper-alpha"?

now reads:

function show()
{
if (isNet4)

document.hidden.visibility = "visible";
}

should read:

function show()
{
if (isNet4)
{
document.hidden.visibility = "visible";
}

clearTimeout is used with the setTimeout while setInterval is used with the
clearInterval.

The DTD is described as defining "how markup tags should be interpreted". This
implies that DTDs provide information on semantics, when in fact they provide
only information on syntax. That is, they define the proper structure of XML
documents, but say nothing about the meaning or interpretation of the tags.

The statement is made that XML doesn't have to be associated with a DTD and
that to convert HTML to XML you should remove the <!DOCTYPE> tag. But XML
documents that are marked as standalone have strict requirements: they cannot
have attributes with default values or entities other than amp, lt, gt, apos,
quot, for example. Converting many HTML documents to XML according to the
rules on page 447 would result in an invalid XML document. Instead, the
converted XML document should begin with something like:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"DTD/xhtml1-transitional.dtd">

A simpler rewriting of "<Element1><Element2>This is content
contained</Element1> in overlapping tags</Element2>" would be
"<Element2><Element1>This is content contained</Element1> in overlapping
tags</Element2>". With this simpler rewriting, there is still only one
<Element2> element. In the more complicated writing, one <Element2> element
has become two, and depending on the semantics of the <Element2> tag (compare
to <p> or <li>), this could change the meaning of the XML.

Is there an assumption that <Element2> tags must be inside <Element1> tags? If
so, this point should be clarified.