Firefox 1.0.1 Released

homeobocks writes "Firefox 1.0.1 has been officially released by the Mozilla Foundation, with some important security fixes. An announcement and release notes are available." Presumably this fixes the window injection vulnerabilities.

Comments

IDN Problems Fixed?

[michaelhood]

From changelog: International Domain Names are now displayed as punycode.

(wiki linkage mine).

Re:IDN Problems Fixed?

[typhoonius]

Anyone who's bored can try out the original proof of concept.

In Firefox 1.0, it displays as "http://www.paypal.com/"; in Firefox 1.0.1, it displays as "http://www.xn--pypal-4ve.com/".

Mirrors

[Anonymous Coward]

If the downloads for Firefox become overloaded today/tomorrow, Coral cache mirrors:

http://download.mozilla.org.nyud.net:8090/?product =firefox-1.0.1&os=win&lang=en-US Windows
http://download.mozilla.org.nyud.net:8090/?product =firefox-1.0.1&os=linux&lang=en-US Linux

Re:Mirrors

[joeldixon66]

From Asa's Blog:

"We're still working on some with the application update infrastructure and the installer so for the first few days, we'll only be offering the release via full download at the website and then turning on the automatic update system hopefully sometime next week."

Re:Mirrors

[Myen]

Since you're linking to the en-US version anyway...
BitTorrent links in case the servers really go to crap. (Theirs, not mine)

Re:Mirrors

[Rirath.com]

I installed 1.0.1, then reinstalled 1.0 because I like the Textzoom extension. This hasn't been officially updated to 1.0, but extensionsmirror has a link to a version patched for 1.0 installs.

Since it's not being maintained, I'll probably eventually have to give it up, but I won't for such a minor Firefox update.

Actually, no you don't. Changing extension maxlimits is trival.

- First, find your profile. In Explorer find: %appdata%\Settings\\Application Data\Mozilla\Firefox\Profiles\\extensions

- Second, open Extensions.rdf with notepad, metapad, etc.

- Third, find and replace any of:
em:maxVersion="1.0"
With em:maxVersion="5.0"

And you're good to go. You can put any number you want, but I like 5.0 just to make it easier, especially with nightlies in the past. You could also use about:config to lower your version number, but that could have other side effects. Now, if doing this makes your extension not work because of code changes (rarely) or somehow borks your profile (highly doubtful), use at your own risk. :)

And Extensionsmirror.nl is a great place to find prebumped extensions.

Re:/. rendering

[damiam]

Oops. On further exploration, I see that it's fixed in the trunk, and the fix will be included in the 1.1 release (I guess must have misread that to say 1.0.1). In the meantime, there's always the SlashFix extension.

OS X-specific fixes?

[moosesocks]

Any word on if this includes fixes for the massive memory leaks in the OS X port? I know they were on track for 1.1, but it's possible they could have made their way into 1.0.1......

Re:Check Updates...

[asa]

We'll be turning on the application update mechanism starting next week. Given the daunting task of updating all 27+ million people who have downloaded and are using Firefox today, we've elected to stagger the update over several days.

--Asa

Re:seems like only yesterday

[jdkincad]

They removed default compatibility for international domain names. I wonder how much of an impact this will have on foreign adoption of Firefox over IE

None. IIRC they just turned off IDN support, and did not remove it. If someone needs it, the can turn it back on.

IE has no IDN support without third party software, so Firefox is still a better choice if you need IDN support.

Actual list of changes

[timealterer]

Here is the full list of changes and related bugs for Firefox 1.0.1.

You'll note that it's quite terse - this is not the 1.1 update from trunk that will get us rendering fixes, etc. that we'll see in June or so. Almost all security fixes here.

Re:seems like only yesterday

[jeffg]

They removed default compatibility for international domain names.

Your statement is misleading.

Support for IDNs is still present, it's just that after inputting a URL using an IDN domain name like http://www.göögle.com/, it is displayed as the punycore representation in the address bar: http://www.xn-ggle-5qaa.com/

The merits of this work around are certainly up for debate (hint: the debate started years ago).

I wonder how much of an impact this will have on foreign adoption of Firefox over IE.

Seeing as no currently shipping version of Microsoft Internet Explorer supports IDNs... you can probably stop wondering. :)

Be kind to the mirrors, use official bittorents!!!

[Jedbro]

Be friendly to the Mozilla.org mirrors, they
have set up an official Bittorent seeder.

-Jed

( http://bittorrent.mozilla.org/ )

Re:But can I upgrade using Software update?

[bersl2]

They are going to enable that in a few days, after those who know about the upgrade have cleared from the servers, lest they be fried.

A few bugs in this release

[CaptBubba]

After installing 1.0.1 on WinXP I could not navigate anywhere. Everytime I would hit enter after typing something into the location bar firefox would crash.

I've gone back to 1.0 and there are no problems. here's a link to the windows 1.0 versions in case anyone else similarly needs to revert back.

Re:How do I automatically kill history in Firefox?

[PReDiToR]

Grab the Kiosk extension from extensionsmirror.nl.

Or you could go to Tools > Options > Privacy > Clear all (under Windows).

Bittorrent!

[GarfBond]

Official BT Torrents here!

Now if you're worried about putting too much strain on the Mozilla download servers, use the BT links!

Alternatively, this page lists translations and direct download links

Re:Check Updates...

[cshields2]

It will most likely not be staggared for the next release, as we will have a major infrastructure upgrade by then allowing the update service to survive the hit all at once. The staggaring had to be done at this point in time.

Cheers!

No more mr. Memory Hog

[Daedalon]

Windows users who have problems with Mozilla software (Firefox, Thunderbird or Suite) being too slow or using too much memory and CPU, check out the Moox optimized builds.

One of my friends reported having constantly about 100 MB more free memory after switching to Moox M2 in his Athlon XP. A bit of a warning though: I tried to install original 1.0.1 over Moox M2 1.0, and it now crashes every time I press enter in the URL bar. Now typing in Internet Explorer, I'm anxiously waiting for Moox optimized 1.0.1 builds to come out and solve the situation.

Re:How do I automatically kill history in Firefox?

[Bagels]

Set it to accept cookies for current session only, have it remember history for past 0 days. Don't worry about the cache, as IIRC it's encoded such that it only means something to the browser (not left with the same title as the cached webpage item or even its extension).

Here is an example.

[maotx]

Here is an example how Firefox 1.0.1 shows IDN names.*
Click the Fake and Real link to see the difference.

The Fake site will not work with Internet Exporer with the latest service pack.

*Requires Firefox 1.0.1

Re:Change Log

[Anonymous Coward]

Firstly, don't plagarise. Cite your sources. Your list is an exact copy of http://www.squarefree.com/burningedge/releases/1.1 .html.

Secondly, if you do plagarise, make sure you steal the right frigging document! You posted a changelog for the not-yet-released Firefox 1.1. This is Firefox 1.0.1. Its changelog can be found at http://www.squarefree.com/burningedge/releases/1.0 .1.html.

Doesn't require 1.0.1

[Theatetus]

Actually you don't need 1.0.1 to see how it works; spoofstick on 1.0 displays the bogus URL as xn--blah-blah-blah...

Re:On this subject

[PeterPumpkin]

Not really, but it can be figured out from this nice chart.

The ad went out on December 16, 2004.

This is 37 days after the launch of Firefox. If you look to the downloads per day graph, there is a noticable increase afterward.

Re:On this subject

[MikeCapone]

www.spreadFirefox.com and Ada's blog at mozillazine.org have most of the information about Firefox's marketshare and marketing campaigns.

I just installed 1.0.1 and everything seems to be working... Except that they haven't fixed the slashdot rendering bug yet (well, to be fair it's probably slashdot's HTML's fault -- I don't know why they haven't switched to CSS yet. They'd save gigs of bandwidth).

Re:On this subject

[dotgain]

BTW the workaround for the rendering bug you encounter on /. is to increase the size of your text then decrease it again (Ctrl +, Ctrl -).

I dunno if it is a slashdot bug or not. It seems to me that if you can fix it with this workaround, then's it's a Mozilla bug (it does it there, too). Yes they definitely should use CSS, but since it's such an ugly site, it'll probably still look better in lynx.

Re:On this subject

[tehshen]

Or you could use SlashFix. I am using it on 1.0.1 and it is working as good as ever.

The main Slashdot rendering bug fix is going to be released with 1.1. This version 1.0.1 is only a security fix.

Re:On this subject

[sepluv]

Except that they haven't fixed the slashdot rendering bug yet

This was fixed in Gecko in May 2004 on the trunk which is used by the latest stable version of Mozilla Suite (but not on the aviary branch which 1.0.1 is still based on. Aviary is now being exhumed back into the trunk, so hopefully, future builds (including releases) will all be based off the trunk (so Gecko fixes will propogate to Firefox).

To fix it in Firefox:

get a recent nightly build--I find them just as stable

just install the Slashfix extension.

BTW the bug only occured sometimes if your machine was fast and it was rendering /. too quickly--you could try reloading--it was a genuine bug as it occured intermittently, but the awful, hoggy, invalid slashcode HTML doesn't help (esp. their use of evil many-nested tables for layout--see the funny and informative Why tables for layout is stupid).