« 2011-10-23 Trunk builds
2011-11-19 Trunk builds »

2011-11-08 Trunk builds

Notable fixes:

  • Fixed: 693743 - 3rd party add-on check doesn't disable those add-ons on start-up, if they were installed into the profile or application folder.
  • Fixed: 693901 - Add extensions.strictCompatibility pref. (Bug 698653 will change the default.)
  • Fixed: 581065 - Allow searching for incompatible add-ons if compatibility checks are disabled.
  • Fixed: 616016 - Visually identify status bar add-on items in the add-on bar while customizing.
  • Fixed: 482921 - Re-implement view source syntax highlighting using the HTML5 parser, and add tooltips for most syntax errors. (Henri's blog post)
  • Fixed: 698929 - Implement event.stopImmediatePropagation.
  • Fixed: 697666 - Don't build the jstracer by default.
  • Fixed: 94199 - Startup speed: Fastload XBL methods and properties.
  • Fixed: 674744 - [Mac] Implement conditional forward button for pinstripe.
  • Fixed: 577867 - [Windows] No way to un-group separate instances on Windows 7 TaskBar.
  • Fixed: 454532 - [Windows] Font glyphs incorrectly displayed with certain printer drivers.

Backouts of changes mentioned in previous posts:

All 812 changes between 2011-10-23 nightly and 2011-11-08 nightly

Nightly builds (discussion)

This entry was posted on Tuesday, November 8th, 2011 at 5:06 pm 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.

5 Responses to “2011-11-08 Trunk builds”

  1. jnz Says:
    November 8th, 2011 at 9:30 pm

    The link to 694432 points to 690227 instead.

  2. Jesse Ruderman Says:
    November 8th, 2011 at 9:41 pm

    Oops, fixed.

  3. Jan! Says:
    November 8th, 2011 at 11:27 pm

    Re: 2011-10-23 Trunk builds

    “Fixed: 451250 – Turn the POSTDATA prompt into an information page (when navigating in session history).” This also fixes “POSTDATA warning should say why the page wasn’t cached”: https://bugzilla.mozilla.org/show_bug.cgi?id=493438, right?

  4. Jesse Ruderman Says:
    November 9th, 2011 at 9:23 am

    Jan, based on the strings added in bug 451250, I’m pretty sure it doesn’t distinguish between the reasons a page might not be cached (which is bug 493438).

  5. Jan! Says:
    November 15th, 2011 at 12:19 am

    Ah, right. Thanks for the clarification.