2005-02-25 Trunk builds

  • Fixed: New options dialog.
  • Fixed: New "Sanitize" privacy feature.
  • Fixed: 131456 - Memory use does not go down after closing tabs (resources not released).
  • Fixed: 278534 - Make tooklit chrome registry use plaintext manifests instead of an RDF cache. (Get rid of contents.rdf chrome registration nightmare.)
  • Fixed: 209020 - Meta HTTP-EQUIV="refresh" broken if midas was ever used in that browser window.
  • Fixed: 198155 - Midas html editing mode persists after leaving the page that enabled it.
  • Fixed: 282103 - Dynamic Overlays.
  • Fixed: 260951 - [Regression] Go menu doesn't display recent page history until second opening (since September on trunk).
  • Fixed: 283046 - [Regression] File input button does not properly render (since Feb 21). (Fixed in Firefox but not in Camino?)
  • Fixed: 283180 - Creativecommons, amazon, eBay, dictionary search plugins are broken for non-ASCII character search.
  • Fixed: 283276 - Plugin finder service freezes when attempting to install plugins and not accepting first license.
  • Fixed: 282764 - Crash when going Back in frameset page [@ nsWindow::UpdateIdle].
  • Fixed: 252189 - Retrieve proper display name for application handlers.
  • Fixed: 125386 - Flyout menu disappears when mouse passes over scrollable div or iframe.
  • Fixed: 244754 - URL is not shown in the status bar when I point at a link on a page encoded as 8-bit Unicode.
  • Since Feb 25: 283600 - Can't open Find as you Type/Find Toolbar.
  • Since Feb 25: 283640 - Hang when opening / closing cookies.
  • Since Feb 25: 283738 - [Linux] Prefwindow V unusable on GTK2+XFT builds.
  • Since Feb 25: Increased leaks on Linux balsa tinderbox (Ben is investigating).
  • Since Feb 25: Crashes while customizing toolbars (?)
  • Since Feb 21: 283355 - Image name and size are no longer displayed in title-bar.
  • Since ~Jan 22: 279497 - Selected profile does not always appear focused.
  • Since ??: 278544 - Location bar of newly created tabs is not focussed after using find-as-you-type (not Ctrl-F); workaround: Ctrl-F.
  • Since ??: 273200 - Ctrl+W in Find bar breaks middle-clicking links, find toolbar, and back button.
  • Since Aviary landing: 272556 - about: is broken.
  • Since Aviary landing: 231361 - Download manager doesn't show downloaded filesize after 1MB if the filesize is "unknown".
  • Missing from trunk: 176177 - History, Bookmarks and Highlight buttons don't have a pressed state in WinXP Luna.
  • Since November on trunk: 269927 - Tooltip appears after closing tab.

The JavaScript annoyance prefs have been removed and replaced by a single checkbox, "but disable common annoyances", under the "Enable JavaScript" checkbox (283716). Checking this box is equivalent to unchecking the first five of the old annoyances options. That is, the new checkbox could be labelled "Don't scripts to (1) move or resize existing windows, (2) raise or lower windows, (3) disable or replace context menus, (4) hide the status bar, or (5) change status bar text" (source code). The sixth and last checkbox from the old annoyances window, "change images", is now gone. As far as I know, these are the only preferences that were in the old Options dialog but not in the new one. [This paragraph was updated and rewritten 2005-02-26.]

There are also a lot of bugs in the new prefs dialog: things that don't work, misspellings, etc. I'm not going to list them all here, but you can find them by searching Bugzilla for "ALL firefox preferences" and sorting by bug ID.

The new "Sanitize" feature lets you clear your tracks quickly with Tools > Sanitize Firefox (Ctrl+Shift+Del on Windows). You can select what data is delected when you use the Sanitize feature. I select Cache and Download History, but someone more paranoid might also select History, Form History, and Cookies.

There are two hidden preferences that change the behavior of Prefwindow V (the new Options window):

browser.preferences.animateFadeIn
When switching prefs panels, change the height of the window and fade the new panel in over about a second.
Default on: Mac.
browser.preferences.instantApply
Changes to preferences are active immediately. The preferences window is not modal. Instead of "OK" and "Cancel" buttons, there is only a "Close" button.
Default on: Everywhere except Windows.

I use Windows. I find that animateFadeIn isn't as smooth as it could be, but I like instantApply.

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

Linux builds: Official Linux, Official Linux installer, alpheratz'

Mac builds: Official Mac, powerbook's

20 Responses to “2005-02-25 Trunk builds”

  1. Jeff Walden Says:

    Do a search in Bugzilla for every bug whose creation date is between 2005-02-24 and Now to get the list of options window bugs that exist. There’s a fair number, and while it’s usable in Windows, Linux GTK2+XFT is right out. (This unfortunately means I can’t do any development work there, but such is life. Hopefully bug 283738 will get fixed soon, because it’s really sucking for me.)

  2. Rich Says:

    Which optimized build to use ? BlueFyre or Moox ?

  3. Ewok Says:

    “Several options are no longer available through the options window; the most-missed preferences seem to be JavaScript annoyances prefs (283716) and disk cache size (283590).”

    Yet again they remove a bunch of stuff that many people used as the main reason for running firefox in the first place.

    This browser is turning more and more into a bluddy IE clone, removing options everyone wants and adding graphical bloated crap like fading windows (so much for the old idea of firefox being lean and not bloated).

    You may well be able to turn the javascript stuff using about:config, but I for one have no idea what options they are, many many less advanced users than me wont even have a clue they exist, and those javascript options are basically the entire reason I moved to firefox in the first place.

    As usual its a case of people being able to program and yet not having the slightest clue about interfaces or what people want. It’s amazing how common that is.

  4. Josť Jeria Says:

    I enabled the browser.preferences.animateFadeIn, it looked pretty cool, but it flickered badly on my win xp. Anyone else seing this?

  5. Jesse Ruderman Says:

    It flickers for me too (using Windows XP).

  6. Josť Jeria Says:

    Would it make sense to file a bug for this? Since its off by default on windows

  7. Jesse Ruderman Says:

    It’s probably a GFX bug involving changes to opacity, not a bug in Ben’s preferences code. Try making a testcase based on Prefwindow V or from scratch.

  8. ts Says:

    While I was thinking good about a new pref window this one is something I really don’t want.

    This new one looks less mac-like than the old one…

    It seems for me as if the wrong prefs have been removed (advanced options for JavaScript) and bloat has been added (Advanced -> Update -> two “check now…” buttons instead of one), FadeIn reminds me on Seamonkey. “about:config” shouldn’t be needed anyway.

    These connection settings thing is still present, most users hate this at least on the Mac.

  9. Foxtrot Says:

    This is a pre-beta release. You can’t expect everything to be perfect yet. I, for one, like it, and I look forward to watching it grow.

    The most severe bug I’ve found is that opening and collapsing a Cookie folder crashes the browser. Also, I think that the category-icons should be centered, and that they have some excess padding that’s noticed when you hover the icon next to the selected category.

  10. Simplex Says:

    Jesse, yes, that’s what I expected too. Often times when doing a transparency fade, you start it off as non-transparent, then go to transparent with an opacity of < 100% and move gradually back up to 100% , and then turn back to non-transparent.

    In Windows, the flicker happens while going from non-transparent to transparent (even with a 100% opacity) and vice versa. That’s been my experience with transparencies, but I know that other programs have found a way to do it right. Weather that is to just leave their window at transparent and just modify transparency? I don’t know.

  11. Hank Roberts Says:

    macupdate.com announced a Firefox 1.0.1, which I did find —
    Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

    but it has the problem of failing when the menu command calls for opening new windows.

    That was fixed Thursday or Friday in the 1.0+nightlies. Which to use?

  12. Hank Roberts Says:

    Hmmm …Maybe this one?
    /pub/mozilla.org/firefox/tinderbox-builds/imola-aviary1.0.1
    firefox-1.0.1.en-US.mac.dmg 26-Feb-2005 21:14 8.3M

  13. Hank Roberts Says:

    Or either of these … “imola” now seems to have Mac OSX builds — “hourly” meaning, I guess, less likely to be good, or unchecked?
    /pub/mozilla.org/firefox/tinderbox-builds/imola-aviary1.0.1

    firefox-1.0.1.en-US.mac.dmg 27-Feb-2005 09:59 8.3M
    firefox-1.0.2.en-US.mac.dmg 25-Feb-2005 16:18 8.3M

    /pub/mozilla.org/firefox/nightly/latest-trunk is unchanged with the 1.0+ Feb. 25th build and the empty Feb. 26th disk image file.

    I wouldn’t fuss over this, I’m just hoping there’s a build that does have the recent security fixes and also does /File/New Window.

  14. Jason Meller Says:

    Ewok: I know this doesn’t really solve the general dillema of giving users with the bare bones browser less and less control over prefs, but for your personal case this extension will re-add the functionality that was removed.
    http://www.blueprintit.co.uk/~dave/web/firefox/jsoptions/index.html

  15. Matty Says:

    I can understand why there’s removal of preferences – look at IE, most people dont even understand 3/4 of the options there and just use defaults. As Firefox has even more functionality than IE, yes it needs configuration but yes most users will also leave things at defaults and don’t need a complicated interface.

    Now, that being said, those of us that do like to push buttons and tweak things to our exact liking also need a way to do so. Maybe there should be a command-line switch -expert or something that will give additional control over the browser.

  16. Dennis J. Says:

    about:config gives you a *lot* of control over the browser. I wonder if there exists a site with documentation somewhere.

  17. geniusfreak Says:

    Dennis J : try here http://preferential.mozdev.org/preferences.html

  18. Dennis J. Says:

    That is exactly what I was searching for. Thanks!

  19. asdf Says:

    The only way to eliminate the flicker in windows is to create the window with the WS_EX_LAYERED style. I’d imagine you’d also be able dynamically do this by clearing the WS_VISIBLE bit, setting the WS_EX_LAYERED bit, and then resetting the WS_VISIBLE bit before calling UpdateLayeredWindow function for the first time.

  20. Hank Roberts Says:

    There’s an OSX 20050203 nightly, but broken somehow — won’t unpack into a disk image (“codec overrun”).

    Pacifict is able to extract and install a firefox.app, but when started up, I see:
    Thread 0 Crashed:
    0 dyld 0x8fe19b28 undo_external_relocation + 0x20c
    1 dyld 0x8fe092ec undo_prebound_images + 0x11c
    2 dyld 0x8fe0192c _dyld_init + 0x224