Phoenix is a redesign of the Mozilla browser component, similar to Galeon, K-Meleon and Chimera, but written using the XUL user interface language and designed to be cross-platform. More information about Phoenix is available at the Phoenix Project Page.
This document covers what's new, download and installation instructions, known issues and frequently asked questions for the Phoenix 0.5 (Naples) release. Please read these notes and the bug filing instructions before reporting any bugs to Bugzilla.
You can now have multiple homepages that will open in tabs upon startup. To use this feature, you can either type in the addresses of the websites you want to use in the Homepage field of preferences (separate them using a "|"), or open the websites you want and then go to Preferences and click Use Current Pages. Please note that this feature is in ongoing development. For example, in the future you'll be able to select multiple bookmarks, and we still haven't decided what to do when you have multiple homepages and open a new window.
You can now use your back and forward mouse buttons with Phoenix, thanks to the fix for bug 30431.
Phoenix will now remember if you had a sidebar open when you quit and will display it when you next start.
Many bugs with the download sidebar have been fixed, including a bunch of cases where downloads remained in the "current downloads" section forever, a bug that caused -1 to be displayed as the progress, and a bug that prevented the progress of downloads with foreign characters in their names from being updated. A download properties dialog has also been added (right click a finished download to access it), as well as some more prefs (one for download directory, one for opening the download sidebar when you begin a download).
The ability to open history items in tabs has been added, and the longstanding bug that history quicksearch was case sensitive has been fixed.
The arrow keys now toggle between focusable elements like buttons, just as on Windows.
Phoenix is lighter than ever before, coming in at 6.1 mb on Windows and 8.7 mb on Linux. And that isn't the end: we've knocked down our target to about 5mb on Windows by the time we reach 1.0, and probably somewhere between 7 and 8 on Linux. These are only guesstimates, please treat them as such. You should also see some decreased memory usage compared with 0.4 (but we still have a ways to go in that area).
0.5 is certainly our fastest release ever. You might especially notice a boost if you have a blank page (about:blank) as your homepage.
Phoenix users using the Classic (default) theme on Windows XP have long enjoyed a browser that blends in with their operating system. With 0.5, people on other flavors of Windows can experience that too thanks to the fix for bug 172751 (the OS now largely draws our widgets on Windows 9x, NT and 2K).
Phoenix theme development has really taken off. Thanks to all the theme authors! Most themes are available here.
But here are some of the most noteworthy. In 0.4, the menubar stayed disabled after customizing the toolbar under certain circumstances, effectively rendering that browser useless. This has been fixed in 0.5. Middle clicking in the content area to go to the address in the clipboard (Linux only) has also been fixed. Some annoying urlbar bugs (like this one) have been plugged, and a longstanding fullscreen bug that made the feature a pain to use is now dead. With 0.5, Phoenix works on Windows 95 again.
Phoenix 0.6 is scheduled to be released sometime in January.
Phoenix binaries are available for Windows, Linux, and OS/2.
Contributed builds (these are unofficial builds and issues should be reported to the build contributor and not Bugzilla).
Localized builds. Contributed by the volunteers of the MLP:
Once you have downloaded the binary, use winzip or gzip to unzip Phoenix to an empty directory. Do not unzip Phoenix to a directory that already contains a binary. Either delete the existing directory, move it out of the way or create a new directory. If you install Phoenix on top of an existing Phoenix or Mozilla directory you will have problems.
To uninstall Phoenix, simply delete the Phoenix directory. This will leave your profile in place for use by future Phoenix installs. If you wish to remove your Phoenix profile you can delete the Phoenix dir from your Windows Application Data directory or remove the .phoenix dir from your linux home directory.
This list covers some of the known problems with Phoenix 0.5. Please read this before reporting any new bugs, and watch it regularly (we'll update it as new bugs are found in the release).
What can I do to help?
We need all the distribution we can get. Tell your family. Tell your friends. Tell your coworkers. If you're a student, get it distributed at your college. Submit a story to Slashdot and other news sites about the release. Make some noise on your blog. Spread the word!
I use another browser because...
If you're not using Phoenix, tell the Phoenix team why. We read all of the feedback at the mozillaZine Phoenix forums.
I sent you mail and you haven't responded.
We do appreciate and read all your e-mail, but may not have time to respond. Please ask questions in the mozillaZine Phoenix forums and report bugs in Bugzilla. Also, please direct all e-mails to email@example.com, the Phoenix developer mailing list. Mail to individual developers that clearly applies to the team is likely to be ignored.
Will I be able to get web content sidebar panels like I can with Mozilla?
Yes, but possibly not until after 1.0.
Is Phoenix as small as it's going to get?
No, we have plenty more to trim out and we're slowly getting to it. Our current targets are 5mb for Windows and between 7 and 8mb for Linux, but these are just guesses. It's entirely possible that we'll beat those (case in point: we had previously targetted 6mb for Windows).
Where can I get Phoenix extensions?
Who is working on Phoenix?
The main developers are Blake Ross, Dave Hyatt and Pierre Chanial. Joe Hewitt also helps us out on occasion. Asa Dotzler provides help doing releases, bug triage, the website, and other odds and ends, and Brian Ryner supplies the build expertise. Please note that Phoenix is a side project for all of us and we may have more pressing issues to attend to as the year draws to a close; inactivity from one or many developers for weeks on end is not unusual. Notes of appreciation, offers to help and most other e-mails should be directed to the team.
Phoenix is a branch from Mozilla so it's going to get old and outdated. It sucks.
No. Phoenix is not a branch; it builds right atop the Mozilla trunk. Each milestone contains trunk code that was literally checked in the day before -- we're risky like that ;) It's the latest and greatest. As we get closer to 1.0, we may need to explore branching or other options to ensure that we have the stability we need.
Okay, so where's the phoenix source?
cvs.mozilla.org. Mozilla trunk + mozilla/browser + mozilla/toolkit.
Phoenix is just Mozilla with a couple UI tweaks.
The 31,000+ lines of code already added or changed from Mozilla beg to differ. People who claim this are generally unknowledgeable about Phoenix.
You said this was designed to be cross-platform. Where's the mac version?
Designed to be cross-platform doesn't mean we offer a build on every platform, it just means the code itself works anywhere. We don't officially offer Phoenix for Mac, but some people have already begun experimenting with mac versions (see this page. We may consider officially releasing Phoenix for Mac in the future, but we want to focus on Windows and Linux for now.
I don't like the stuff on the toolbar.
View | Toolbars | Customize...
I hate the theme you're using.
So get another one. We are considering changing the default theme in the future, but haven't made any decisions yet.
I kept hearing that you were changing the name from Phoenix to something else. What happened?
That was just a giant publicity stunt. We've observed that in the past, the open-source community has instinctively favored David when big corporations complain of trademark infringement. We wanted to cash in on this sympathy by asking the community to send us money to fight the legal battle (obviously we'd really spend it on cool stuff), but with all the taxing issues and whatnot we decided to can the idea.
No, not really. This isn't like an action flick where the evil madman reveals the intricacies of his plans to hostages and then leaves them alone with a bomb set to detonate in like 10 hours. When we're ripping you off, we won't explain how in the FAQ. The truth is that we'd already had this 0.5 released planned for awhile, so it was okay to release under the Phoenix name. But under no circumstances will any future release be called Phoenix.