2004-10-24 Branch builds

  • Fixed: 265692 - Mouseover child of link (e.g. image link) does not show url in status bar (since Oct 22).
  • Fixed: 265774 - Ctrl-enter on a link is nonfunctional (since Oct 22).
  • Fixed: 265135 - Can't install extensions from https://update.mozilla.org/ (since Oct 19).
  • Fixed: 246173 - [Linux] Install failed: Couldn't open xpistub library.
  • Fixed: 251586 - Select tag with multiple and size set create lists with out scrollbars if the option tag labels are all numeric.
  • Fixed: 259683 - Padding-top results in space below float too.
  • Fixed: 252345 - Memory leak in nsXMLHttpRequest.cpp (seen when using GMail).
  • Fixed: 265721 - Remove -moz-key-equivalent to prevent crashes.
  • Fixed: 234169 - Asgard plugin crash.
  • Fixed: 265728 - Security hole.
  • Since Oct 21: 265839 - External protocol handling broken.

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

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

Mac builds: Official Mac, PowerBook's

10 Responses to “2004-10-24 Branch builds”

  1. BlakeRG Says:

    I REALLY hope hey fix bug # 243324 before the 1.0 release. Its been around for a while and its very annoying especially if you’re a shoutcast lover like me. Anyone how/if its possible to get a bug added to the list blocking 1.0?


  2. James Kilfiger Says:

    As for bug 243324, it’s not going to be made a 1.0 blocker. It has been considered (by Ben or Blake or one of the other firefox honchos) and they have decided it doesn’t block 1.0, and in all likelyhood 1.0 will ship with that bug. Sorry.

    But, hey don’t these builds look very RC1? 265839 will be fixed tomorrow.

  3. Scott Says:

    I have a naive question: why do there seem to be so many nasty regressions lately, as 1.0 gets closer? Isn’t that a bad thing?

  4. Hank Roberts Says:

    Scott — a naive answer (I’m just a crash dummy) — I think it’s like having half a dozen people making the bed, whenever someone tucks something in one one side, something gets pulled out or wrinkled on another side. It takes a while …

    Meanwhile, is the “download error” for extensions when trying them from Mozdev this one?

    “Fixed: 265135 – Can’t install extensions from https://update.mozilla.org/ (since Oct 19)”

    265235 still shows as a live bug.
    I still get “download error” trying Mozdev.

    Other extension authors I’ve contacted seem puzzled when I report lack of success with their releases since 1.0; I’m wondering how many of them have tweaked a setting to avoid version problems, forgotten about it, and just aren’t seeing problems!

  5. Hank Roberts Says:

    My typo above, 265_1_35 — one person reports it’s fixed on the bug report page, but unless I’m misreading the info it isn’t fixed for sure.

    I still get “download error” from the link listed as working for mozdev extensions, as of right now.

    Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041025 Firefox/1.0

  6. Anonymous Says:

    > Other extension authors I’ve contacted seem puzzled when I report lack of success with their releases since 1.0;

    You are aware that 1.0 has not yet been released?

  7. Jesse Ruderman Says:

    All four recent regressions (265839, 265692, 265135, 265774) were caused by buggy fixes for three security holes.

  8. Hank Roberts Says:

    >you are aware

    Yes, I over-shortened the name, didn’t I? Tonight I”m using — according to “About Mozilla Firefox” —
    “version 1.0 RC1
    Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041025 Firefox/1.0.”

    I pointed these discussions out to one extension author, whi didn’t know and thanked me:

    Extensions will be broken starting with Oct 16 nightly

    Extension Version Update (Firefox 1.0 / Thunderbird 0.9)

    Bumping extensions, using old ones on new builds

  9. mat Says:

    does anyone has an idea what theese builds are

  10. Hank Roberts Says:

    Tue 26th Oct 2004 1:33am Firefox Roadmap
    New Releases

    Additional required work has necessitated the insertion of a new release for Windows, Linux and MacOS X (0.10 – called “1.0 Preview Release”) and extra for MacOS X (0.11 – coincides with “1.0 Final”). The decision has been made to hold the 1.0 release on MacOS X until after 0.11 has been completed, basically ensuring that we do not ship a product that is not up to spec for that platform.

    Bottom of the site “New Releases”