This page lists unconfirmed errors and comments from readers.
They have not yet been approved or disproved by the author or 
editor and represent solely the opinion of the reader.

Programming Firefox, 1e
by Kenneth C. Feldt

The catalog page for this title is http://www.oreilly.com/catalog/9780596102432/

This page was last updated Mon Mar 31 16:18:21 EDT 2008.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy
or the digital version accessed.

Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem


UNCONFIRMED errors and comments from readers:


(40-41) Between the bottom of page 40 and the top of page 41;
Between pages 40 and 41, there is an unmatched pair of ".
Plus the parameter 'type="text/css"' seems to be included where it isn't needed at the top of page 41.

So:

The " are opened on the 3rd line of the code fragment:

<?xml-stylesheet href="........

They are never closed (and I think they should be at the bottom of page 40 maybe)

And then page 41 starts with:

type="text/css"?>

the " is never closed, and I don't think that the 'type="text/css"' is required either, as it is 
specified on the 3rd line of the code already.


{44} 1st paragraph, 2nd line;
The example referred to has the pack property set to "center", not to "end" as mentioned in the text.


{55} Code example, top of page;
First two lines of the .xul file should read:
<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

instead of:
<?xml version="1.0"?>
<?xml-stylesheet href="testStyles.css" type="text/css"?>

If one makes that change then the second and third button respond.

As far as a I can tell "testStyles.css" is not defined any where in the book. Looks to me like some 
section on CSS files got edited out (probably from section 2.9 "Mozilla Stlye Declarations").


[55] Top of code listing;
The window.onload example will not work with Firefox 2.0 as written. The 'testStyles.css' file has not 
been created yet but it is referenced at the top of the newssearch.xul file. When Firefox fails to load 
the stylesheet it will also fail to fire the 'onload' event. Firefox will not display any kind of error.

To fix this example you can either removed the stylesheet reference from newssearch.xul, or create an 
empty 'testStyles.css' in the same directory you have newssearch.xul.


{72} Section 3.4.2.3. The DOM Inspector;
DOMi DOM inspector is not installed by default on Firefox 2.0. See

http://geekswithblogs.net/TimH/category/3314.aspx/rss

User needs to
a Run the Firefox 2.0 install again.

b Choose to do a Custom install (not the default of Standard)

c Make sure DOM Inspector is selected.

d Complete the install.


{105} Bottom;
The name of the stylesheet being used has changed in the source code listing from "testStyles.css" to 
"NewsSearchStyles.css" with no mention in the text about this happening. Also, changes to the scripts are 
usually in bold, this one is not.

The stylesheet must exist or else the XUL window's onload event will not fire.


(314) 2nd paragraph (of text);
The 2nd ACTUAL paragraph (3rd if you include the code fragment) reads:

"The file xblText.xml would include the following:"

I think it is supposed to read:

"The file xblTest.xml would include the following:"

(xblTe_S_t, not xblTe_X_t)