Errata

Programming Firefox: Rough Cuts Version

Errata for Programming Firefox: Rough Cuts Version

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 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.

 Anonymous   
Printed Page 44
1st paragraph, 2nd line

The example referred to has the pack property set to "center", not to "end" as mentioned in the text.

 Anonymous   
Printed Page 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").

 Anonymous   
Printed Page 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.

 Anonymous   
Printed Page 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.

 Anonymous   
Printed Page 79
last paragraph

This isn't really an error, but you talk about putting the manifest file in the chrome directory. I got burned because there is more than one chrome directory! There is the application's chrome directory, but there is also a chrome directory in each profile. Putting a manifest file in the profile/chrome/ directory does not work (at least for me on MacOSX). One of those "mantrap" icons would be really helpful here!

 Robert P. Goldman  Jan 04, 2010 
Printed Page 85-87
Anywhere

There should be some mention here of the cross-domain limitations of using an XMLHttpRequest object. Perhaps even pointing the user to https://developer.mozilla.org/En/HTTP_Access_Control or a similar resource could save some headaches. Or just place this at the top of doCommand.php:

header('Access-Control-Allow-Origin: *');

with a comment explaining the purpose of that header.

Paul Osman  Oct 03, 2009 
Printed Page 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.

 Anonymous   
Printed Page 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)

 Anonymous