Slashdot Mirror


Firefox 1.5 RC2 Available

ltwally writes "Although not posted on the Mozilla website yet, Firefox 1.5 Release Candidate 2 is out. You can grab it here. As of right now, it is available for Linux (i686), Mac OS X and Windows. Happy updating!"

20 of 297 comments (clear)

  1. If you have 1.5 RC1... by puppetman · · Score: 5, Informative

    It will automagically do the update (after asking you first). Mine did about 3 hours ago.

    My Help->About still says plain old 1.5, however.

    1. Re:If you have 1.5 RC1... by gregbains · · Score: 5, Informative

      Mine didn't automatically do this, but a quick help->update and all sorted, thanks again Slashdot for keeping me up to date :)

    2. Re:If you have 1.5 RC1... by Martin+Blank · · Score: 4, Funny

      It's new to 1.5, and is an attempt to improve office productivity.

      --
      You can never go home again... but I guess you can shop there.
  2. Only en-US so far... by iworm · · Score: 4, Interesting

    The update, at the time of posting, is only available for en-US builds so far. Now I know that that's all that matters, but if you're running RC1 non-en-US then the update might be a little time away yet.

    Perchance that's why it's not been publicised yet, and further perchance that's what the poster or editors might have noticed? Sorry, dreaming there for a moment...

  3. Re:Fire--- by EnronHaliburton2004 · · Score: 4, Funny

    And perhaps you should ask on the Ubuntu forums? We're not really technical here, we just pretend to be ;)

  4. Please save Mozilla.org some bandwidth by Critical_ · · Score: 5, Informative

    If you're running RC1 already, the posted links have .MAR files available to perform an update without redownloading the entire binary. Windows users should be careful because .MAR is associated with Microsoft Access in Office 2003 (maybe earlier versions but this is all I checked with). Anyway, info on how to update with .MAR files is here:

    Manually Installing a MAR File

    ----
    Car pictures gallery

  5. Re:What exactly is wrong... by the+real+darkskye · · Score: 4, Informative

    There is nothing wrong for people updating from 1.5-beta or 1.5-RC1 as the update is only around 360Kb.

    Its probabably preferable for moz.org to let as many people grab the tiny update before anouncing the availablility of the 5Mb full installer.

    When 1.5 goes gold however, you will have a very valid point, because I know that _I_ will be replacing my existing Firefox Setup 1.5 Beta 1.exe with the final version.

    --
    Music is everybody's possession.
    It's only publishers who think that people own it.
    Fuck Beta
    ~John Lenno
  6. Changelog by Anti-Trend · · Score: 4, Informative
    I went to hunt down the changelog, and since I had to compile a list of changes from a few sources I will go ahead and reproduce the whole thing here:

    * Fixed: 314241 - "Report broken web site" toolbar button is broken when using "small icons".

    * Fixed: 313490 - Enable IDN for .org.

    * Fixed: 313894 - Reporter chrome is registered twice.

    * Fixed: 313360 - Profile locking doesn't work if the profile is located on a FAT partition.

    * Fixed: 314754 - "Extension compatibility updates" check never completes.

    * Fixed: 314684 - Endless update loop from firefox 1.5 beta2 to 1.5 rc1 if 1.0.x was ever installed

    * Fixed: 312777 - Negative margins cause floated elements to be placed to the right of incorrect earlier boxes (since March 2005).

    * Fixed: 312363 - document.write into iframe results in broken-lock icon

    * WFM: 314484 - Firefox 1.5 RC1 topcrash [@ 0xffffff4d] [@ js_GC]

    * Fixed: 309044 - Flashplayer 8 "Bad NPObject as private data!"

    * Fixed: 314258 - ExtensionItemUpdater:checkForDone: Failure in listener's onAddonUpdateEnded.

    * Fixed: 315017 - [Linux] Undetermined progressmeter doesn't work.

    * Fixed: A few potential security holes.

    * Fixed: 313414 - Add a way to do "sandboxed" http connections that don't modify the cookie list.

    * Fixed: 314465 - Implement a non-copyingCompareUTF8toUTF16.

    * Fixed: 263042 - Ship both autocomplete impls with the new-toolkit

    * Fixed: 264308 - Implement DOM Level 3 UserData API.

    * Fixed: 314218 - New version of JEP (0.9.5+a), please land on trunk and branch.

    * Fixed: 147670 - Wrong (last or empty) tooltip text displayed for dropdown list menu items.

    * Fixed: 226094 - Support JavaScript Core for WinXP AMD64.

    * Fixed: 314549 - Various bugs involving containers not actually fixed for subframes.

    * Fixed: 312036 - History.dat contains entries deleted from the "date and site" view.

    * Fixed: Several fixes for specific DHTML performance tests.

    * Fixed: 312804 - No longer shows loading-image.gif when loading images

    * Fixed: 309706 - Stack overflow crash [@ jpinscp.dll + 0xaa87] (since Sept 22).

    --
    Working in a DevOps shop is like playing in a band made up entirely of keytarists.
    1. Re:Changelog by jesser · · Score: 4, Informative

      If you're going to copy information from The Burning Edge without attribution, at least get it right. You included several bugs that were only fixed on the trunk.

      --
      The shareholder is always right.
  7. Hooray, SVG support! by Max+Threshold · · Score: 4, Funny

    Now I can embed SVG images into my pages. Exported from OpenOffice Draw, of course. "This site best viewed with a modern browser. Get Firefox 1.5 now, you Neanderthal!"

  8. Re:advancements/innovation? by zulux · · Score: 4, Insightful

    It seems like most of the advances that Firefox made vs. IE have now been neutralized [snip] What new ideas/innovations are the Firefox team making these days to stand out in the browser wars?

    Security.

    Internet Explorer still is an ActiveX exploit away from wiping you files.

    --

    Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

  9. Re:load time by WiFiBro · · Score: 4, Informative

    Yes to me that was the most noticable change. Especially the first time you run it is very fast. They also worked on the speed of going forward and backward.

  10. Does it fix the friggin' clipboard bug? by Maxmin · · Score: 5, Informative

    Under Windows XP, Firefox has become my browser of unchoice, because it's clipboard functionality is totally borked. I posted to bugzilla, and saw that about a million other people have too.

    --
    O lord, bless this thy holy hand grenade, that with it thou mayest blow thine enemies to tiny bits, in thy mercy.
    1. Re:Does it fix the friggin' clipboard bug? by DarkEdgeX · · Score: 4, Interesting

      Yeah, this happens to me as well. I usually do Ctrl+C and Ctrl+V to copy from the address bar to an open chat window in another application, and sometimes it will, for seemingly no reason, not work. Sometimes I'll even try Ctrl+X (cut), and sure enough, when I do this the text disappears from the address bar (indicating it recognized the cut operation), but it still won't paste! Just to verify it's not the chat app but Firefox, I open Notepad and still can't paste.

      Oddly, if I beat the unholy shit out of Ctrl+C it will, sometimes, eventually work. Sometimes.

      --
      All I know about Bush is I had a good job when Clinton was president.
  11. Re:advancements/innovation? by Ythan · · Score: 4, Interesting

    I think extension support is the single most significant feature of Firefox. Sure you can add functionality to IE but it's not as easy as packaging up some Javascript. This extensibility lets Firefox support new and unimagined features without adding bloat. It wouldn't surprise me if IE moves in this direction eventually just to stay competitive.

  12. Re:load time by Ythan · · Score: 5, Informative

    Debunked, but still a common misconception.

  13. Firefox 1.5rc2 is nearly ready to be announced by Anonymous Coward · · Score: 4, Informative

    The Firefox 1.5rc2 release is nearly ready to be announced. When it is, we'll update our website to point you to the installer files with links that use our load balancer. A note: going to our FTP site directly will hammer all mirrors evenly which is bad for those smaller mirrors that aren't as bandwidth-laden as our bigger mirrors.

    If you can't wait for your Firefox 1.5rc2 fix, though, feel free to download Firefox 1.5b2 or 1.5rc1 and then use software update (Help -> Check for Updates...) to grab the 1.5rc2 update. The updates for both to 1.5rc2 are less than a meg!

    Chase, the build/release guy at Mozilla

  14. Re:Firefox "update" feature sucks by alfrin · · Score: 4, Informative

    Do you pay any attention? The new 1.5 Firefox has binary updates, eliminated that problem all together.

  15. Re:advancements/innovation? by digidave · · Score: 4, Informative

    What are they doing? With 1.5...

    1. Improved the rendering engine (through Gecko)
    2. Better tab behaviour (drag and drop placement, better default behaviour)
    3. New faster updates that don't require a reinstall
    4. SVG support

    And more, but I can't remember every big change from the changelog at the moment. Don't forget that this is a minor release, not a major release. It's mostly refining and improving features from 1.0. You can expect bigger changes in 2.0. With any luck, 2.0 will be out in time to greet IE 7.

    --
    The global economy is a great thing until you feel it locally.
  16. Re:Repeated updates by masklinn · · Score: 4, Informative

    If you are using a Beta version (and not a Release Candidate), then it checks on the Beta/Dev branches, which means that it has a news version (new build) pretty much every day.

    Try doing this: go to the config page (type about:config in the address bar), then search for "app.update" and set the values:

    app.update.channel to release app.update.url to https://aus2.mozilla.org/update/1/%PRODUCT%/%VER SION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL% /update.xml app.update.details to http://www.mozilla.org/products/firefox/releases /

    That should do the trick and grab the updates from the Release files (aka stable branch) instead of the beta/dev files

    --
    "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler