Creating Applications with Mozilla
|resources:||Home Chapters Examples Figures Corrections Bugs Resources Mailing List Authors Reviews|
If you find any errors in the book, please feel free to enter a new bug to report the problem. The bug report will be taken and the fix will be incorporated into the next printing of the book. The basic process for making corrections follows these steps:
- Anyone is welcome to enter a new bug. People can also report problems on the email@example.com mailing list or in the User Notes section for each chapter. Community members will take reports posted there and file a bug with the information.
- One of the authors will take the bug report and verify the problem. If a correction is needed they will update the HTML version of the chapter with the fix.
- After the HTML has been fixed, the bug should be reassigned to firstname.lastname@example.org. He will update the corrections page with the fix and then close the bug.
- When it is time to prepare for the next printing of the book, we will send the fixes listed on the corrections page to O'Reilly and they will update the book accordingly.
Here are the bugs relating to DocBook updates
Latest bugs filed for books
|14935||missing image file|
|7489||Chapter 1 sidebar mentions Firebird instead of Firefox|
|7045||Wrong menupopup id in example 10-17|
|6278||Problem in nsSimple.cpp|
|5970||Tips for rregistering the packages|
|5541||books.mozdev.org // html generation // move|
|5328||Home page updates|
|5317||Create a jar file (and XPI) of the book with complete navigation|
|5316||new xul book jar|
|5024||Win2000 Problems with "var f = new File('/tmp/foo');|
To receive access to edit bugs for this project, please contact the project owner.