Slashdot Mirror
Firefox 1.5 Final Now Available
yootje writes "Firefox 1.5 is out, you can download it right here: Linux; Mac; Windows. You can find more info about it in the release notes. Highlights are: Automated update, drag and drop reordering for browser tabs, improvements to popup blocking, better accessibility and better support for Mac OS X. Don't forget to make full use of the mirrors." It's semi-official.
You would think that they could build packages for at least the most popular linux package management systems. Wonder how long til this shows up on the DAG repository...
For the people using Windows:
Gnutella, G2 and ed2k go here.
torrent can be found here.
Normally this means the server is sending the file as some binary format, file extensions don't matter. Try this Ubuntu torrent which works for me.
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
It seems very nice so far. I'd been using RC3 for a few days now. All extensions carried over for me, although I had to reset my Tabbed Browser Preferences.
One of the nicest new features is the "Unable to Load" page that comes up instead of the alert that interupted your browsing, even while in another tab, on the older versions.
Some of the rumorous new tab features haven't made it in so far, which is a shame. They're supposed to make tabs work more like Opera: Close tab returns to previous tab, and close box on each tab, as well as cleaning up the text in tabs. Oh well, overall very nice though.
put the what in the where?
No, RC3 is just a release candidate. They haven't updated the pages because it's not officially out yet (check mozilla.org, newest is "1.0.7" according to that), however, the FTP directory for Firefox has 1.5 final (which usually means that the offical release for Firefox 1.5 is the next day, so it will probably be out tomorrow or later this week).
RC3 build string:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Release build string:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
RC3 MD5 hash:
d0cbbd5d8c47fe36ee8f26fb1255838c
Release MD5 hash:
d0cbbd5d8c47fe36ee8f26fb1255838c
RC3 SHA1 hash:
fb6bed8635ff06e76cfde326e8dc5776b4efdb66
Release SHA1 hash:
fb6bed8635ff06e76cfde326e8dc5776b4efdb66
They would appear to be the same thing.
You can never go home again... but I guess you can shop there.
See previous discusions about firefox and Acid2. Mainly it involves making serious changes to the Gecko layout engine. The changes were to risky for the 1.5 Firefox release. From the roadmaps it does not look like Firefox 2.0 will pass either.
9 31679= 12465304
http://slashdot.org/comments.pl?sid=167091&cid=13
http://it.slashdot.org/comments.pl?sid=148742&cid
These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
Does anyone know why Safari passes, but no other browsers?/ 1336223&tid=121&tid=106this story.
Konquerer does with KDE 3.5 released today. Check out http://linux.slashdot.org/article.pl?sid=05/11/29
This can happen for two reasons.
(1) the server uses content-disposition: attachment. In this case, the server is arguably telling the browser "do not open this file automatically". I'm not sure why Firefox cares that the server says that, though. See bug 236541.
(2) the server uses content-type: application/octet-stream. In this case, I think it's a browser bug. I'm not sure this still happens.
You might be able to tell which it is using web-sniffer.net or LiveHTTPHeaders.
The shareholder is always right.
Please do *NOT* download it from ftp.mozilla.org. Please instead use our redirector, which has a lot more bandwidth:
o s=win&lang=en-USo s=osx&lang=en-USo s=linux&lang=en-US
o x/releases/1.5/
Windows: http://download.mozilla.org/?product=firefox-1.5&
Mac OS X: http://download.mozilla.org/?product=firefox-1.5&
Linux: http://download.mozilla.org/?product=firefox-1.5&
Or, if you need a different language, get it from releases.mozilla.org, which doesn't have as much bandwidth as the redirector but still has *much* more than ftp.mozilla.org:
http://releases.mozilla.org/pub/mozilla.org/firef
What he meant is the HTTP server isn't configured to send torrents with application/x-bittorrent as the Content-Type. Instead, it sends them as a generic application/octet-stream or worse text/plain which Firefox doesn't know what to do with.
Note that Firefox 1.5 RC3 is the exact same as Firefox 1.5 down to every last bit. So if you already have RC3, you already have the final release. You don't need to download it again.
Why? Well, because RC3 was the last release candidate, and having the last release candidate be exactly the same as the final release is the best way to ensure that all the testing the release candidate gets definitely applies to the final. Otherwise we would have run the risk of any change, no matter how minor, introducing a problem that we didn't foresee.
So they're the same. Right down to the user agent string, the version number, etc. Do an md5sum on both files, and you'll get the same values. You get my drift.
OK, but for case (1) ("Content-disposition: attachment"), you've still asked FF to save it to disk automatically. In particular, it SHOULD NOT ask "Do you want to save this?". Ever.
Even if there isn't "; filename=" on the Content-disposition header, you can guess at one by removing the last path element of the request URI. FireFox already asks for filenames much less often than Mozilla, so I don't want to see a filename request, either.
I have heard that manually adding an "application/binary" entry in Helper Applications will prevent that; apparently, FireFox and Mozilla don't actually save the choice you just made for that MIME type.
I think I did it on at least one of my machines, and have since forgotten if I did and/or if it worked. Which isn't very helpful... but Safari saves without prompting just fine.
Does anyone know why Safari passes, but no other browsers?
Someone got annoyed that Safari did not pass and wrote patches to fix it. The KHTML team ported those patches so they also now pass the Acid2 test. Other developers have worked on fixing Gecko so that Firefox passes, but the changes required are fairly radical so they have thus far refrained from implementing them since they are afraid of breaking things. The IE team does not give a rat's ass about old standards, let alone newer ones or edge cases and will likely never pass. So to answer your question, because the Safari/KHTML codebase is neat and because someone felt like fixing it.
From http://wiki.mozilla.org/Firefox:1.1_Product_Team:
FIREFOX 1.5 RC3
Firefox 1.5 RC3 was released on 2005-11-17.
If no showstopper issues are identified with this build, it will be released as Firefox 1.5 (Final)
This is the 3rd Release Candidate (RC3) for Firefox 1.5, addressing any regressions or other bugs uncovered in the 2nd Release Candidate (RC2). It is officially branded as Firefox 1.5 and has been released to the community for testing and quality checking. It is of production quality and is also a final opportunity for Extension, Theme, l10n and web application developers to finalize their support for Firefox 1.5 before final release.