« 2007-04-13 Trunk builds
2007-04-26 Trunk builds (Gecko 1.9 Alpha 4 RC1) »

2007-04-22 Trunk builds

Fixes:

  • Fixed: 84582 - Stylesheet loading blocks parser.
  • Fixed: 323656 - Frames with anonymous box inside cause broken inheritance.
  • Fixed: 85872 - Inheritance from elements with display:table-cell broken.
  • Fixed: 346994 - Remove leading dot (period) (.) from suggested filename for saving (save file).

Fixes for recent regressions:

  • Fixed: 374873 - Find returns to top immediately after first instance in form field.
  • Fixed: 377473 - One Tooltip Listener II: And in the darkness crash them [@ nsXULTooltipListener::LaunchTooltip].
  • Fixed: 373693 - Cycle collector makes AddRef about 6x slower.
  • Fixed: 377606 - Switch cycle collector to more efficient hashtables.
  • Fixed: 374872 - Freeze/pause after clicking on a link? (related to cycle collector).
  • Fixed: 372838 - [Windows] Print preview is broken.
  • Fixed: 377779 - [Mac] New version of JEP (0.9.6.2) to fix a Java crash regression.
  • Fixed: 363574 - [Mac] Favicons/site icons missing from Bookmarks menu in Cocoa builds.

Trunk regressions:

  • Since Nov 22: 361523 - [Mac] Form borders are too thick.
  • Since Jan 26, 2006 (FDL): 324819 - Fixed positioned elements now lag/flicker when scrolling.

Trunk checkins between 2007-04-13 04:00 and 2007-04-22 04:00

Windows builds: Windows nightly (discussion)

Linux builds: Linux nightly

Mac builds: Mac nightly

This entry was posted on Sunday, April 22nd, 2007 at 8:25 am and is filed under Trunk. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

One Response to “2007-04-22 Trunk builds”

  1. René Says:
    April 26th, 2007 at 1:40 am

    hi there,

    this might just be a personal feeling. but on my powerbook switching from one tab to another / scrolling etc. takes a lot longer when using my external keyboard (bluetooth) compared to when using the internal keyboard. i haven’t experienced that behavior with other applications, so i was wondering whether that is a firefox bug and whether other people have experienced that behavior aswell.

    cheers, rené