Slashdot Mirror
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.
From changelog: International Domain Names are now displayed as punycode.
(wiki linkage mine).
If the downloads for Firefox become overloaded today/tomorrow, Coral cache mirrors:
t =firefox-1.0.1&os=win&lang=en-US Windowst =firefox-1.0.1&os=linux&lang=en-US Linux
http://download.mozilla.org.nyud.net:8090/?produc
http://download.mozilla.org.nyud.net:8090/?produc
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.
It's hard to be religious when certain people are never incinerated by bolts of lightning.
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......
-- If you try to fail and succeed, which have you done? - Uli's moose
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
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.
The great advantage of having a reputation for being stupid: People are less suspicious of you.
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.
- Allen Pike
Altering time, one time at a time.
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).
Seeing as no currently shipping version of Microsoft Internet Explorer supports IDNs... you can probably stop wondering.Be friendly to the Mozilla.org mirrors, they
have set up an official Bittorent seeder.
-Jed
( http://bittorrent.mozilla.org/ )
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.
As I mentioned in the story, 1.0.1 contains fixes for 9 security holes, some of which allowed spoofing.
MOUNT TAPE U1439 ON B3, NO RING
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.
Grab the Kiosk extension from extensionsmirror.nl.
Or you could go to Tools > Options > Privacy > Clear all (under Windows).
Do not meddle in the affairs of geeks for they are subtle and quick to anger
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
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!
That's not actually a popup, it's just an image inside an with CSS "position: absolute". There's no way to stop this unfortunately, blocking absolute positioning would screw up a lot of site's layouts.
My computer is 4 years old now and Firefox is not a dream to use as it keeps freezing up for 2 seconds whenever its CPU usage maxes out. K-Meleon is much lighter, though not as pretty
Secondly, FF is NOT faster, despite the FUD that FF zealots like to spread. I've timed both and it takes FF several seconds longer to start up as well as to render a complex page.
/. story with browser speed comparison. Opera is faster, but IE is actually faster than Firefox in most operations.
Well said... Check previous
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.
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).
--- Bwah?
Seriously, you need to spend a little more quiet time with google. +firefox +popup +blocking +tutorial
It's not hard. I see nothing except for the odd tiny fraction of css crap.
Fix it yourself because - 'they' - will never hold your hand until it works just nice and peachy the way you personally want.
If a site you like has more advertising than actual content, then maybe you need to go elsewhere. The net is a pretty big place, apparantly with lots of duplication...
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
I'm a virgo and on Slashdot. Coincidence? Yes.
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.
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...
All's true that is mistrusted
yes you can.
go to -> Windows Task Manager -> view -> select column -> check virtual memory size
kawai
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.
Memory cache device
c he
Number of entries: 208
Maximum storage size: 31744 KiB
Storage in use: 7436 KiB
Inactive storage: 7127 KiB
List Cache Entries
Disk cache device
Number of entries: 312
Maximum storage size: 50000 KiB
Storage in use: 18025 KiB
Cache Directory: C:\Documents and Settings\Development\Application Data\Mozilla\Firefox\Profiles\fd8vwgvl.default\Ca
Liberty freedom are no1, not dicks in suits.
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).
Treehugger? Treehugger... Treehugger!
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.
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.
Guy asked me for a quarter for a cup of coffee. So I bit him.
I would imagine that this could also be added to a proxy easily enough also.
Sometimes people just have to learn and adapt to change, it is one of the requirements of being a living thing.
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).
Joe Llywelyn Griffith Blakesley
[This post is in the public domain (copyright-free) unless otherwise stated]