2005-09-08 Branch builds (roughly Firefox 1.5 Beta 1)

Fixes for regressions:

  • Fixed: 307235 - Compatibility checker checks endlessly (since ~Aug 31). (There was also a server-side fix, so users with older builds won't encounter this as often.)
  • Fixed: IDN blacklist doesn't work due to a bad patch for bug 301694. Fixed by backing out that patch.

No major regressions since Deer Park Alpha 2.

Gecko 1.8 branch checkins between 2005-09-07 15:00 and 2005-09-08 06:00

Windows builds: Windows nightly, Windows hourly (discussion)

Linux builds: Linux nightly, Linux hourly

Mac builds: Mac nightly, Mac hourly

5 Responses to “2005-09-08 Branch builds (roughly Firefox 1.5 Beta 1)”

  1. nex Says:

    hi, my english is not very good .. so, if anyone of you can report this bug … if you have gmail try changing the default language for spanish and you will see how left menu looks bad (with this build, but with 1.0.6 looks good).

  2. Uri Bernstein Says:

    nex, what you are describing is bug 301411.

    Jesse – you might want to have a look at that bug. It seems as if it were a Gmail browser-detection bug, yet it regressed at a point where the User-Agent string did not change – so it must be something else.

  3. Max Says:

    It will be a shame if bug #252371 (incremental find/search in page does not find/highlight text in textarea/form/text entry boxes) is still there in FF1.5 final. 219 votes in bugzilla say it all – THIS BUG NEEDS TO BE RESOLVED! Why isnt Mozilla Foundation doing anything about it???????? You can´t say you have the best browser available if you cant search within textarea, form or entry boxes e.g. in wikis, weblogs, CMS…

  4. agarwaen Says:

    Which build should I download, beta 1 of firefox or the one from today? Is already beta1 code in todays 1.8 mozilla branch?


    and will it be better to download


    when it will be avaiable?

    thank you

  5. rodii Says:

    Max, everyone thinks their pet bug is the crucial one. All you can do is talk it up, make your case, vote for your bug, or contribute a patch if you can. There’s no need to be dramatic about it–there’s no shortage of bugs in any browser, and everyone’d doing the best they can.