2007-06-15 Trunk builds


  • Fixed: 110161 - Enable OCSP by default.
  • Fixed: 242621 - Move Autoscroll icon out of the page's DOM.
  • Fixed: 383803 - Places Tagging Back-end (nsITaggingService).
  • Fixed: 295498 - Middle-clicking autocomplete entries opens the URI in the same tab instead of a new one.
  • Fixed: 384034 - Update to breakpad revision 189.
  • Fixed: 329846 - Enable native theme in HTML content on Linux.
  • Fixed: 371360 - Scripts can tailgate departing users with onUnload.
  • Fixed: 345517 - Build Firefox --enable-libxul (not static) by default. (But not yet on Mac -- see bug 384269.)
  • Fixed: 383010 - Visual glitches while scrolling pages with position:fixed elements.
  • Fixed: 384100 - Word-based textrun cache.
  • Fixed: 381031 - Make JS1.8 the default for <xul:script>.
  • Fixed: 383234 - Various cycle collector debugging patches.
  • Fixed: 332649 - [Windows] Need better font switching mechanism.

Fixes for recent regressions:

  • Fixed: 342810 - Threadmanager checkin 2006-05-10 causes increased memory usage by ~10MB per minute with Flash (memory leak?).
  • Fixed: 382541 - [Mac] Add a hidden pref to make Breakpad not suppress the Mac OS X crash log.

Trunk checkins between 2007-06-01 04:00 and 2007-06-15 04:00

Windows builds: Windows nightly (discussion)

Linux builds: Linux nightly

Mac builds: Mac nightly

3 Responses to “2007-06-15 Trunk builds”

  1. Lee Says:

    Oh wow, they can’t fix bug 242621! That will break the thing on hixie.ch!

  2. ant Says:

    Does 329846 mean we don’t need to look at those ugly Windows-ish form controls any more? Finally!

  3. Per Ångström Says:

    I’ve been having problems with printing in the latest Linux trunk builds. This build doesn’t crash (as was the case with a few earlier ones), but print-prepare is slow and it hangs the browser completely (no redraw, almost 100 % CPU usage) until it is finished.

    With “slow” I mean that moderately complex pages can take over a minute to prepare. This comment page takes some 15 seconds, and that’s on a dual-core 2 GHz processor. I think that’s unacceptably slow.