2004-10-04 Branch builds

  • Fixed: 258767 - Shift+Delete to remove autocomplete results crashes Firefox (since Sept 15). (Fixed at 11AM, before the official Windows builds but after the official Mac and Linux builds.)
  • Fixed: Divert featureless window.open calls to tabs.
  • Fixed: 248432 - Unable to uninstall extensions which have not finished downloading.
  • Fixed: 254662 - "Don't exit" dialog boxes exits anyway.
  • Fixed: 252182 - Extensions are not correctly re-enabled after -safe-mode.
  • Fixed: 247884 - Upgrading doesn't remove the old entry from Add Remove Programs - Windows.
  • Fixed: 258892 - When changing themes, Firefox reverts to uninstalled theme if you fail to select a new theme.
  • Fixed: 242393 - Topcrash: After dowloading page [@ nsHttpChannel::OnDataAvailable ].

If you select "Force links that open new windows to open in: a new tab", Firefox diverts links with target="_blank". It also diverts JavaScript window.open() calls, but only calls that don't specify window features (e.g. size and which toolbars are displayed). Most calls to window.open() specify the size of the window. You can change this by setting the browser.link.open_newwindow.restriction pref in about:config.

  • 0: divert window.open() (what I use)
  • 1: don't divert window.open()
  • 2: divert window.open() without features (default)

Windows builds: Official Windows, Official Windows installer (discussion), bangbang's

Linux builds: Official Linux, Official Linux installer, daihard's

Mac builds: Official Mac

13 Responses to “2004-10-04 Branch builds”

  1. Oakwine Says:

    Regarding the “JavaScript window.open() calls” checkin; is there a bug that discusses this, or was it just checked in on its own? It seems to be messing up Bloglines.com, which appears to use javascript.doLoadf(), and the three options you listed don’t make the problem go away. It worked fine on 20041002.

  2. Oakwine Says:

    Nevermind. I had added the preference as a string instead of as an integer.

  3. denis Says:

    Before I install it: does this build work well with TBE (any conflicts after the single-window mode was added?)


  4. CooLynX Says:

    It deletes all the history.dat data and does not save any new entries. :(

  5. CooLynX Says:

    After some tests I could not get to work my old history.dat file. Looks like there are some changes in format or something like that. So you should be aware that history.dat will start from scratch but it works fine. Too bad for such lazy bastard as me. ;)

  6. Jesse Ruderman Says:

    My history is intact. I’m using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041004 Firefox/0.10.

  7. laszlo Says:

    > Does this build work well with TBE?

    It does for me. TBE’s settings for external links have stopped working, but since Firefox now offers its own settings it doesn’t matter.

    > My history is intact.

    Same here, no history problems. I updated from 20041001.

  8. stonedyak Says:

    Is the new single-window mode turned on by default? I hope it is, since this will make discovering tabs a lot easier for new users.

    I saw a Firefox review a while back where the reviewer thought that you needed an extension to enable tabs!!

  9. Boris Says:

    Hmm.. what do the redirected window.open calls return? What if the site then tries to access the “newly opened” (it thinks) window?

  10. Jesse Ruderman Says:

    Boris, I tested it briefly last night and window.open() seemed to return the correct window object.

  11. CooLynX Says:

    Maybe it was because I used Installer version.

  12. linux Says:

    Perhaps we should stop hiding the tab bar by default and add the new tab button to the tab bar, so newbies will be able to find it eaiser.

  13. David Janes Says:

    I love the new tab controls but browser.link.open_newwindow.restriction defaults to zero instead of two which makes some sites not work (see enclosed bug).