What kind of a roar can we expect from such a cute, cuddly creature as a firefox?
Posted by: Kob on November 8, 2004 01:05 PMDid we get 8 million downloads from 0.10? SFX hasn't been updated since the 5th...
It would be great if we did!
Posted by: Doug Wright on November 8, 2004 01:22 PMDoug, yeah, we passed 8 million a couple of days ago. I intend to try to update the counter one last time but that depends on how much time I have :-)
--Asa
Posted by: Asa Dotzler on November 8, 2004 01:24 PMI can barely contain my excitement. I hope all the mirrors are prepped ;)
Are there plans for moz to officially support a BT distribution scheme sometime?
I'll add to the roar IF (and only if) Bug # 255732 is fixed. Until then, it's back to 0.9 for me. Sorry to say. Firefox as currently offered is. not. usable. on the Mac for people who surf weblogs and click links that generate new windows using a javascript command. Like comments, of which the blogosphere has myriads. Or web-based email. Sad story here. Don't know how I can help other than the voluminous Talkbacks I've been sending. Cheers and congratulations otherwise, Asa.
Posted by: Susan Kitchens on November 8, 2004 01:39 PMplease don't scare little children with these scary logos ;)
good luck with Firefox 1.0. lets blast away for 10mil dls..
Posted by: z on November 8, 2004 01:49 PMWell Susan, its fixed in 1.0! The "fixed-aviary1.0" keyword means its fixed on the code branch where Firefox 1.0 is developed.
Posted by: Fredrik on November 8, 2004 01:50 PMSusan Kitchens: wasn't this bug fixed about two weeks ago???
Posted by: aku on November 8, 2004 01:50 PMThis is like the day before Christmas! :)
Posted by: David Tenser on November 8, 2004 01:53 PMIt's fixed? Cool. I'll await the new release tomorrow. For today: safari.
Posted by: Susan Kitchens on November 8, 2004 02:10 PMI've just seen the new graph on SFX - wow!
I am kinda worried about 8 million auto-updates hitting mozilla.org at once though - the server handling redirects to mirrors is gonna get hammered!
Posted by: Doug Wright on November 8, 2004 02:45 PMYeeeee! ;-)
I cannot wait until Firefox 1.0
But tell me, what about Thunderbird? When it will hit 1.0? Previous releases (0.7, 0.8) were nicely aligned to correspondinf Firefox release and it would be nice to get Thunderbird 1 at the same time as Firefox 1 (not to mention possible joint marketing push).
BTW, it's already 9th in Europe ;-)
Posted by: alex_t on November 8, 2004 03:40 PMEep! Big scary lizard! :-O
Alex, I think Thunderbird was planned to go 1.0 more or less the same time as Firefox 1.0.
My best wishes to the Mozilla team who has put all their effort into this.
Let the followers of Mammon cover in horror once and for all this time. :-)
Posted by: Jugalator on November 8, 2004 03:46 PMI'm quite unhappy with the change in behavior with browser.block.target_new_window in bug 266490. This makes my browsing experience much less pleasant and I have no intention of using 1.0 with this behavior. I want window.open() to open a separate window for popup forms and I want links with target= to be forced to open in the same tab like my nightly builds still do. The new prefererences force me to open both popup windows and target links in a new tab, which is not at all elegant. Very bad show, chaps.
Posted by: Programmerman on November 8, 2004 04:36 PMProgrammerman, I think it's customizable!
Posted by: alex_t on November 8, 2004 04:45 PMProgrammerman, actually the UI for browser.link.open_newwindow is gone in RC2. Not sure about the final build...
Posted by: minghong on November 8, 2004 04:52 PMI set the browser.tabs.showSingleWindowModePrefs setting to true in about:config to turn the tab preferences back on. It doesn't help me though. The behavior is different from nightlies no matter what I change the settings to.
Posted by: Programmerman on November 8, 2004 05:10 PMProgrammerman: if true, then that's a very bad show indeed.
1) target="_blank" and window.open(NORMALCHROME)
2) window.open(DISABLECHROME) and window.open(LIMITCHROME)
These two link opening techniques mean entirely different things. (1) means "open a page somewhere else without changing this page". (2) means "open a special window with particular window features".
If they are equated, it means you get a very ugly experience when you intend (1) but get (2), or intend (2) but get (1).
Their proper meanings should be the default behaviour (based on the user's other tabbed preferences).
Posted by: voracity on November 8, 2004 05:23 PMI'm sure the mirros will go download with the ammount of traffic from the number of people download and especially from all the auto updates. What will happen if autoupdate trys to download and the server is offline? will they get an error message or what? Just wanna make sure firefox wont crash or something if the servers are down.
Posted by: Kurt on November 8, 2004 06:23 PMCongratulations to the Mozilla team!!
I hope to be able to grab a copy to do the last testing for SiteBar Sidebar 1.0
It's a luxury container for the SiteBar bookmark server to fit in Firefox.
This combination is like your bookmarks in the sidebar but it is a client->server solution.
Anyway i am not going to spam it here further, interested people will google for it, others wont.
I just put this here because like you i am excited with the Firefox 1.0
Thanks for the bumpy ride since 0.5...
I've been waiting for this day since Phoenix 0.4, and I'm sure others have been waiting longer. Thanks to the developers and the community.
(Which reminds me... have you donated yet? :-)
Posted by: Will Price on November 8, 2004 10:45 PMAll I can say is "Congratulation! 1.0 is you!" :)
Congrats and thank you to the developers and everybody else who made it possible.
Programmerman, you can get the behaviour you want by setting browser.link.open_newwindow.restriction in about:config. The current default value is 0, which is to intercept all window.open() calls. I have it set to 2, previously the default, which allows window.open() calls that do things like setting the window size still to open in a new window. You can also set it to 1, which allos all window.open() calls to open windows.
Details here (though remember the default has changed since then):
http://www.squarefree.com/burningedge/archives/000590.html
I would have e-mailed you this, but I'm guesing your address is fake, so I'm hoping you'll just happen to come back to this blog entry several hours later ...
Posted by: Smylers on November 8, 2004 11:35 PMFor 2+ years phoenix/firebird/firefox has been my primary browser. It's been truly great watching it grow and mature over that time...I wanted to give a thanks to all the devs who make my favorite piece of software possible...including all those people who download and bugtest every release. Just a few more minutes till midnight here...so I'm gonna go pick up my copy of Halo2 and maybe if I'm lucky there will be a Fx 1.0 waiting for me when I get back.
Thanks again go out to Asa, Ben and the rest.
Posted by: flatrabbit on November 8, 2004 11:35 PMAnd it's out. Although I grabbed my copy from the ftp directory a few minutes before the official announcement went up ;-)
Posted by: James on November 9, 2004 01:13 AMUm..
I see 1.0 is out.. I decided to point my friends to http://www.mozilla.org/mirrors.html
However, I noticed that you have to scroll down to get to the links, whereas you do not have to in IE.
*hugs*
Posted by: larfnarf on November 9, 2004 01:15 AMSmylers, thanks a lot. That setting seems to work. This doesn't seem very safe to be making changes like that so late in the game before a release. Also wish there was an advanced GUI panel to change these settings instead of editing prefs directly.
Posted by: Programmerman on November 9, 2004 04:38 AM