You are probably reading this after running into a bug or some other annoyance in MultiZilla. That is too bad, and we're sorry, but now it is up to you to either completely ignore the bug or annoyance, stop using MultiZilla, wait for us to miraculously fix the problem for you...or help us fix the bug.
Reproduce the Bug
Gatter the Required Information
Report the Bug
Cool. Read on...
Launch Error Console
There are two ways to launch the Error Console in SeaMonkey with MultiZilla:
The first two errors in this screenshot are caused by a problem on
line 331 in the file multiviewsTabs.js It's part of the MultiZilla source,
because it starts with chrome://multiviews/ We are only interested in
warnings and errors that start with chrome: Here are some
examples for you:
The last two errors on the screenshot are not part of the MultiZilla source code. However, these errors can still be caused by a third party add-on, so we might need them to fix the bug.
Okay, say you've launced the Error Console and found a Warning/Error in the MultiZilla source code, or you think it is. Now, search in the MultiZilla bug database (bugzilla) and file a new bug in case you can't find a duplicate for it. Copy the text from the console to the bug report and add steps to reproduce.
JS Protocol Filter
Note: The new features were introduced in a prior version of MultiZilla and are very useful for web-developers/designers and bugtrackers, but it was already being used before thatby HJ and Neil. You might consider reading this Mozilla bug report where you can see how old this thing really is.
Cascade Style Sheets errors
SeaMonkey is constantly changing its XUL code so we have to keep up with some of these updates. This can cause serious problems. Make sure to test your bug with the most recent MultiZilla version available for the installed SeaMonkey version. We won't fix bugs for older SeaMonkey versions; you simply have to update your SeaMonkey build in case you run into this kind of troubles.
SeaMonkey has a build in debug console. You can start SeaMonkey with: seamonkey -console to launch it. It's very useful in case SeaMonkey doesn't startup, especially after installing third party add-ons/themes. Check if you see chrome: related errors on the console. This information might help us to fix bugs even quicker.
Third party theme support
MultiZilla is designed for the two default mozilla themes, Classic and Modern. We don't support other themes. You should always test your bug with the default Classic and Modern themes. We're not going to install all available themes. Theme errors must be fixed by theme authors because we don't do that.
There are several ways to run into profile errors with SeaMonkey and MultiZilla will also suffer from this kind of problems. You should always try a new profile, before you file a bug report.
Start SeaMonkey with: seamonkey -profilemanager and select Create Profile. And check if that helps.
It is a good habit to check if the bug is caused by SeaMonkey, MultiZilla, or the combination of the two. You must also disable other installed extensions/add-ons, because they can also cause problems.