Errata

HTML: The Definitive Guide

Errata for HTML: The Definitive Guide

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.

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.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 9
1st full paragraph

The URL for W3C is:

http://www.w3.org

Anonymous   
Printed Page 43
last item on HTML list

You include <param> in a list of "HTML tags that do not have corresponding
ending tags," and on page 437 no end tag is indicated, but in Desktop Reference
fold out and on pg. 525, <param> is followed by </param>.

Which is correct?

Anonymous   
Printed Page 48
Section 3.5.1.2, second paragraph

Now reads:

"ja" (Japanese), and "hi" (Hindu).

Should read:

"ja" (Japanese), and "hi" (Hindi).

Note "Hindi" vs. "Hindu" typo.

Anonymous   
Printed Page 49
Top of page in constant-width font

the SGML <!doctype> reads:

<!DOCTYPE HTML PUBLIC "-//W3C/DTD HTML 4.0//EN"
"http://www.w3.org/TR/html40/strict.dtd">

however, the www.w3.org says at

http://www.w3.org/TR/REC-html40/intro/sgmltut.html that the <!doctype> tag

should read:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">

(Note the missing slash after W3C, 4.0 is now 4.01, and html40 is now html4)

Anonymous   
Printed Page 57
3.9 The <bdo> Tag, first paragraph

"These language-related attributes, then, may effect some display
characteristics"

should be

"These language-related attributes, then, may AFFECT some display
characteristics"

Anonymous   
Printed Page 84-85
Concerning <sup> and <sub>, it is written that the text is displayed

"half a character's height higher [or lower], but in the same font and size as
the current text flow." That is not what I find. For example,

1999<sup>1999<sup>1999</sup></sup>

produces incorrect results in Internet Explorer 4.0 (version 4.72.3110). The
first superscript is a smaller font size. The superscript of the superscript
is in the same size AND AT THE SAME HEIGHT as the first superscript! On the
other hand, Netscape 4.5 produces a nice result, but still each subsequent
superscript is at a smaller and smaller size, as well as being raised.

I tried to kludge Internet Explorer into doing the right thing by altering the
SIZE of the final superscript, but it appears that Explorer steadfastly
refuses to acknowledge a nested instance of
<SUP>. Bummer.

Anonymous   
Printed Page 86
In Table 4-2

<s> display style strike should have a line through the word strike. <u>
display style underline should be underlined if these items are to conform
with the rest of the entries.

Anonymous   
Printed Page 163
5.5.1.1

Describes the <marquee> tag takes the attribute of ALIGN (values TOP MIDDLE
BOTTOM) - I do not think the <marquee> tag takes an ALIGN attribute.

It has no effect when I try it (viewed with IE 5) and the Mircrosoft Website
does not list it as an attribute of <marquee>.

FYI The Microsoft website page with this information may be found at:

http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/
MARQUEE.asp

Of course Microsoft does not indicate which version of IE the elements listed
are for (4.0 -5.0 ??), so it may simply have been eliminated in the 5.0
version of IE.

Anonymous   
Printed Page 173
6.1.1.3, 2n para:

"in pixels"

should be

"in pixels or percentage"

(as you state in 6.2.1.3, page 179, end of para 1).

Anonymous   
Printed Page 182
The Javascript command


warning.visibility = show;

should read:

warning.visibility = "show";

Anonymous   
Printed Page 188
On line -7 (6.3.1.6):

"in pixels"

should be

"in pixels or percentage"

(as you state in 6.2.1.3, page 179, end of para 1).

Anonymous   
Printed Page 195
First paragraph:

should read: "h, t, t, p, colon, slash, slash, w, w, w, dot, widgets, dot,
com" (The 1st dot was missing.)

Anonymous   
Printed Page 221
last line

Text says "Mosaic as shown in Figure 7-4" but Figure 7-4 (on page 222)
displays Internet Explorer icon instead of Mosaic icon.

Anonymous   
Printed Page 231
HTML fragment near end of subsection 7.5.4.2

Change "75,75,99,99" to "50,50,99,99" if you really mean the 100x100 image's
lower-right quadrant.

Anonymous   
Printed Page 231
second paragraph under subsection 7.5.4.3 and associated HTML fragment

Text says "lower-left quarter" but fragment says "75,75,99,99" (which is the
lower-right eighth of a 100x100 image. If you really mean the lower-left
quadrant, the fragment should say "0,50,50,99". If you want the lower-right
quadrant, change the text from "lower-left" to "lower-right" and change the
fragment to "50,50,99,99".

Anonymous   
Printed Page 234
subsection 7.5.5

HTML fragment implies juice on left and soup in center of image. Figure 7-7
shows soup on left and juice in center.

Anonymous   
Printed Page 241
2nd paragraph

The book states quite clearly: "you can make the base URL relative, not
absolute." Not according to the W3C HTML 4.0 specification (24/4/1998
revision) which states: "href = uri [CT] This attribute specifies an
***absolute URI*** that acts as the base URI for resolving relative URIs." (My
emphasis.)

My own tests with relative hrefs confirm this.

Anonymous   
Printed Page 254
1st example

The sixth line of the example:

H1: {color: blue; font-style: italic}

has a superfluous colon. It should read:

H1 {color: blue; font-style: italic}

Anonymous   
Printed Page 271
In the 1st para


"IE 4.0, ... in the spring of 1997"

should be updated to:

(IE and N support CSS1 and partly CSS2)

Anonymous   
Printed Page 271
2nd paragraph or 1st full paragraph

Book refers to a separate "compliance document" on how style sheets are
implemented by latest browser releases. It says to look for the document at
http://www.oreilly.com/catalog/9781565924925.

When I went to that URL, I saw a description of the book, but no link to the
document. Where is it?

Anonymous   
Printed Page 271
3rd para:

"all the components" should be changed since this chapter didn't cover ALL
components (e.g. cursor, multi columns, MS special filters).

Anonymous   
Printed Page 273
Delete 9.1.2.1 "you may omit the type attribute ...": type has to be

used.

Anonymous   
Printed Page 273
9.1.2.2:

last para needs to be updated since N4 and IE4 so support the media attribute,
though only partly.

Anonymous   
Printed Page 274
9.1.3.1

http://www.kumquats.com/styles/gen_styles.css gives error 404.

Anonymous   
Printed Page 284
section 9.2.4.5, last line of first indented code block

The line reads:

A.fancy:active {text-weight: bold; font-size: 150%}

I think it should be FONT-weight, and not TEXT-weight.

Anonymous   
Printed Page 285
On line -1 (9.3.1.2):


"in pixels"

should be

"in pixels or percentage"

(as you state in 6.2.1.3, page 179, end of para 1).

Anonymous   
Printed Page 286
On line 5:

"in pixels"

should be

"in pixels or percentage"

(as you state in 6.2.1.3, page 179, end of para 1) and change "two" in line 3
to "three".

Anonymous   
Printed Page 286
1st para:

Since pixels are relative they should be removed from 1st line and "three"
should be changed to "two".

Anonymous   
Printed Page 289
9.3.3.2, 1st para, 2nd line:

Since pixels are relative they should be removed from 1st line and "three"
should be changed to "two".

Anonymous   
Printed Page 291
In row 7

... with an extra 24 points of space between ...

Should be 48 points.

Anonymous   
Printed Page 292
The last para of 9.3.4.2 should be removed since N4 does support

background-color.

Anonymous   
Printed Page 293
The last para of 9.3.4.4 should be removed since N4 does support

background-color.

Anonymous   
Printed Page 297
2nd para of 9.3.5.2:

Percentage and scaling factor are relative.

Anonymous   
Printed Page 308
2nd last para of 9.3.6.10:

N4 does support margin.

Anonymous   
Printed Page 309
Last sentence of 9.3.6.11:

N4 does support margin.

Anonymous   
Printed Page 311
In the last row:

[width property, 9.3.8.1]

should be display property.

Anonymous   
Printed Page 321,325
It mentions that <method> and <action> are required for <form> tag.

But I don't think they are required. The parameters can be passed through
hyperlink to a ASP file without a submit buttom.

For example,

<a href="updateshippingoptions2x.asp?shippingID=<%
=rsShipMeth("pk_id") %>&amp;action=up"><img
src="/images/up.gif" border="0"></a>

The parameters can be passed without a submit buttom!

Anonymous   
Printed Page 325
Section 10.2.3

"in the HTML 4.0"

should read either

"in HTML 4.0" or "in the HTML 4.0 standard"

"browser may chose to"

should read

"browser may choose to"

"The default value of this attribute is unknown, implying
that form character set is the same as the document
containing the form."

should read

"The default value of this attribute is unknown, implying
that the form character set is the same as that for the
document containing the form."

Anonymous   
Printed Page 327
1st paragraph

The following sentence contains a double negation (cannot not) which is surely
not intended (?):

Before id was introduced in HTML 4.0, Netscape used the
name attribute to achieve similar effects, although it
cannot not be used in a hyperlink.

Anonymous   
Printed Page 331
second bullet in subsection 10.4.1

Change "including as some versions" to "including some versions".

Anonymous   
Printed Page 348
3rd. par

"This the most useful way"

should read

"This is the most useful way"

Anonymous   
Printed Page 359
legend box

In the <legend> box, it now reads:

End Tag:
</optgroup>; may be omitted

This should be:

End Tag:
</legend>; never omitted

Also, the "Contains", and "Used In" info needs correction also.

Anonymous   
Printed Page 365
10.11.2.1:

Using named parameters with GET applications ---- in the code:
I get errors while compiling the code in the

TYPEDEF Struct (char *name;
char *val;
}entry;
^------------

Should read Entry (case sensitive).

Also, the program SHOULD return a value, at least a RETURN();.

Also, while linking with previous corrections made:

Linking ECHOHTML.EXE:
Linker Error: Undefined symbol _makeword in module ECHOHTML.C
Linker Error: Undefined symbol _unescape_url in module ECHOHTML.C
Linker Error: Undefined symbol _plustospace in module ECHOHTML.C

Anonymous   
Printed Page 380
last paragraph of subsection 11.2.2.2

"Neither dir nor lang are yet supported"

should be changed to

"Neither dir nor lang is yet supported."

Anonymous   
Printed Page 400
last sentence in subsection 11.3.8

"Internet Explorer support"

should be changed to

"Internet Explorer supports"

Anonymous   
Printed Page 406
Third line from the top, after the number 4

I think it should read "supported" instead of "sport", right?

Anonymous   
Printed Page 413
Inset box

The </frame> end tag occurs in various places: under the description of the
frame element, the quick reference on p.511 and the attached card.

However, it cannot be produced from the grammar or DTD, and on page 43 is
explicitly said not to exist.

It's an unfortunate error, as it suggests that omitting the tag is sloppy
HTML, whereas actually the reverse is true.

Anonymous   
Printed Page 430
<object> table at top of page

"CODE" is not listed as a supported attribute of the <object> tag;
nevertheless, the "CODE" attribute is used in the example at the very bottom
of page 431. Furthermore, that example does work fine with IE4.0 (while the
example using 'CLASSID' immediately above it does not).

Anonymous   
Printed Page 433
On line 5 of 13.2.1.7:

"in pixels or percentage" (as you state in 6.2.1.3, page 179, end of para 1)

Anonymous   
Printed Page 441
On line 5 of 13.2.3.7:

"in pixels or percentage" (as you state in 6.2.1.3, page 179, end of para 1)

Anonymous   
Printed Page 441
13.2.3.8:

Please check this. Isn't it the opposite? (mayscript indicated that JavaScript
will be accessing Java features)

Anonymous   
Printed Page 442
13.2.4:

In the box and end of 13.2.4.1: align is supported by IE.

In the box and between 13.2.4.4 and 13.2.4.5: the pluginurl attribute is
missing.

Anonymous   
Printed Page 445
summary of <noembed> tag

"End tag" says "none". The example on the next page shows </noembed> end tag.
I think "End tag" should match the example, otherwise, how will "<embed>-aware
browser know when to resume HTML interpretation?

Anonymous   
Printed Page 446
Maybe you want to mention IE's tag for AVI videos as 13.2.6.

Anonymous   
Printed Page 450
In line -5:

Remove <frameset> ? (onLoad and onUnload can be used in <frameset>)

Anonymous   
Printed Page 464
6th Para. Section 14.2.1 "Uniquely Refreshing"

Re <meta http-equiv="Refresh", book say that Web Servers spot this element in
the page and convert it into a HTTP Header that it sends to the browser.

This is not the case, no Web Server that I know of parses static HTML files
looking for <meta http-equiv= headers. Instead the client (Browser) in
parsing the page finds such elements and appends corresponding HTTP Headers to
those it received from the server.

This error is repeated also on pages 246 and 247 in Section 7.8.1.3.

Anonymous   
Printed Page 488
all three code samples

I believe the rows and cols attributes for the frameset tags are misleading.
If what is meant is a two-by-two layout then "50%,50%" should have been used.
Also, the second nested frameset tag in the first code sample is missing a
cols attribute and the last code sample has a cols attribute when I believe it
should be a rows attribute.

In addition I am confused by the sentence which reads: "The trick is to
replace frames B and D with a single frame...". There is no explanatory text
which explains how one might go about doing this replacement. How do you
replace the initial frameset with the second code sample without disturbing
the contents or scroll position of frames A and C when someone clicks on a
link in frame A? If someone can better explain how to accomplish this task I
can be reached at rmroczk@sears.com.

Anonymous   
Printed Page 516
description of taborder attribute under input type=checkbox

Change "Specifu" to "Specify".

Anonymous   
Printed Page 530
last line:

Just a suggestion: move last line to next page (it's sort of a header, and
there is enough space on the next page).

Anonymous