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!"
← Back to Stories (view on slashdot.org)
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.
Modify your shortcut: "C:\Program Files\Mozilla Firefox\firefox.exe" /Prefetch:1
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
It is a bug in RC1 - the only "what's new" entry for RC2 is "several fixes to automated update system". I was getting the same thing on Beta 2 for RC1 - I eventually uninstalled Beta2 to install RC1 fresh.
1 .5.html
The transition from RC1 to RC2 was smooth, however.
http://www.mozilla.org/products/firefox/releases/
[DISCLAIMER: This post is a work of satire and should not be misconstrued as a holy text upon which to base a religion.]
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
* 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.
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.
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.
Debunked, but still a common misconception.
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
memory problems
I haven't seen any memory leaks since I upgraded to 1.5. Normally if I leave Firefox
pointing to a page that refreshes often, the memory will swell to 150MB on my Windows box within 24 hours.
But I haven't seen that problem with 1.5.
94% of Repubs and 21% of Dems voted to renew the Patriot Act
http://www.mozilla.org/products/firefox/releases/1 .5.html
Switch to Adblock Plus http://forums.mozillazine.org/viewtopic.php?t=2662 91
I'm the urban spaceman babe, but here comes the twist... I don't exist
Do you pay any attention? The new 1.5 Firefox has binary updates, eliminated that problem all together.
Well it doesn't seem to work with the w3c's svg test suite....
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.
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%/%VEThat 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
Just in case some don't know, in the upcoming IE 7, ActiveX is at least now an opt-in feature.
Beware: In C++, your friends can see your privates!
IANAMD (I am not a Mozilla developer), but I assume there is no RC2 in the version string because for once they are actually adhering to the meaning of "release candidate". If they find no show-stopping bugs in this build, the exact same file you just downloaded will be rechristened "Firefox 1.5". If they had to change anything (even the version string), it wasn't technically a "candidate for release".
Rock over London, Rock on Chicago. Wheaties: Breakfast of Champions.