2004-06-23 Trunk builds

Fixes for regressions:

  • Fixed: 246213 - Background colors and images are not shown.

Fixes for other bugs:

  • Fixed: 246618 - Show Default Download Folder in Downloads Window when in AutoDownload mode.


  • Since ~June 10: 246168 - [Linux] '-remote "openURL(<url>, new-tab)"' no longer works
  • Since May or June: 246687, 246658, 248013 - Firefox startup gets stuck at "Finishing Extension Installation" for various reasons. (Workaround: run "firefox.exe -no-extensions" and disable the extension responsible, or delete the extensions subdirectory of your profile.)

Windows builds: Official Windows, Official Windows installer (discussion)

Linux builds: Official Linux, Official Linux installer

Mac builds: Official Mac

9 Responses to “2004-06-23 Trunk builds”

  1. Matthew Trent Says:

    Extensions seem to be broken enough to make them unusable in official 0.9 and in CVS. Wouldn’t be such a big deal, except, IMHO, Firefox isn’t very usable without them (in the area of tabs, specifically).

  2. Karl He Says:

    Extensions are very usable inside Firefox 0.9.

    The thing is, for 0.9, the profile directory migrated from Application Data\Firefox to Application Data\Mozilla\Firefox, so you need a new profile for everything to work properly.

  3. Matthew Trent Says:

    I’ve completely removed my firefox directory, so it’s not that. Extensions just seem a bit buggy right now.

  4. Karl He Says:

    I don’t mean your firefox directory, I mean the profile directory.

  5. Walter K Says:

    In my experience, there is another workaround. If I get “Finishing Extension Installation” message, I’m able to run FF by clicking on FF icon again. Then, when a new window opens, I’d just go back to the “Finishing Extension Installation” message and close it. After that, extension manager shows which extensions are misbehaving and have to be disabled and/or removed.

  6. Jean-Marc Gillet Says:

    (A subjective opinion follows.)
    From what I read in the forums, the EM, at least in terms of image, is a failure for Firefox. You cannot advertise (on mozilla.org at least) a 0.9 version that could well be feature-complete but has a lot of *visible* bugs for these features as well. Either you’re very discreet about it, or the release is delayed …

  7. Mark B Says:

    I have to agree with Jean-Marc. I know everybody wanted to reach the 0.9 milestone, and there was a lot of pressure to do so, but I think it would have been wise to wait a few more days (or even weeks) as necessary to work out the kinks with the EM. Karl, even if you start entirely fresh (uninstall FF, manually remove profile, and manually edit out crap from Registry), there are *still* problems with the EM hang on startup depending on the extension. I did this (e.g. total cleaning), installed a recent aviary build, went to update.mozilla.org and installed AdBlock and BugMeNot extensions, and then ran into the EM hang on startup problem. Unfortunately, it was the BugMeNot extension (v0.3). Even though that extension was supposedly updated on 15 June and thus should be in the new EM format, well, it still seems to choke the 20040620 or later Aviary builds. I ended up having to manually delete the extensions directory in my profile just to start. Walter K. had an interesting work around, so I’ll be sure to try that next time around. So anyway, I wouldn’t have minded waiting some more…

  8. Karl He Says:

    Why am I not getting any problems then…ah oh well.

  9. Scott Says:

    didn’t have any problems here either. I have a total of 8 extentions installed.