Today we have our first Firefox 1.0 candidate builds available for testing. If all goes well in testing these builds, then we're on target for our 1.0 release in early November. If you're interested in testing these candidates and reporting bugs to Bugzilla, you can get them from FTP. If you've already downloaded 1.0 PR (the "feature complete" preview) and you're not particularly interested in active testing and bug reporting, then you should probably stick with 1.0 PR for a couple more weeks and upgrade when we release the official Firefox 1.0.
Things that need special attention in this RC include:
The release candidates include about 250 bug fixes since Firefox 1.0 PR and we'd appreciate any feedback around any of those areas. If you can help in verifying (feel free to skim the bug titles and find ones that interest you) that would be great!
With this release, we're also featuring Mozilla Foundation builds for up to two dozen locales (slowly trickling in. if you don't see your language, try back in a bit.) These builds are hot off the press and haven't received as much testing as we'd like so if you're a non-English user, or speak any non-English languages, we'd encourage you to download one of the new localized builds and hammer on it some. The more testing we get at this stage, the easier time we'll have releasing all these localizations when we ship the en-US builds on November 9.
If you do find regressions from the Preview Release, please file bugs in Bugzilla and nominate them as Firefox 1.0 blockers using the "blocking-aviary1.0?" flag on the bug. Thanks for your help in testing Firefox!
Posted by asa at October 27, 2004 02:36 PMAny ideas of when the source be made available?
Posted by: Hanspeter on October 27, 2004 03:06 PMHanspeter, the source is always available. http://www.mozilla.org/cvs.html
--Asa
Posted by: Asa Dotzler on October 27, 2004 03:56 PMVery nice.
Posted by: XeroCool on October 27, 2004 04:04 PMasa, shouldn't i be able to cancel de update?
Posted by: kwanbis on October 27, 2004 04:08 PMI've just filed https://bugzilla.mozilla.org/show_bug.cgi?id=266340 about icon creation.
Posted by: Doug on October 27, 2004 04:15 PMafter the update, i got this error (after restaring ff)
http://nodo9.com/ffrcerror1.jpg
Posted by: kwanbis on October 27, 2004 04:16 PMnote, i fixd y installing from the installer
Posted by: kwanbis on October 27, 2004 04:19 PMOops, nevermind on that application update mechanism testing. We have a nasty crash bug there ;-)
--Asa
Posted by: Asa Dotzler on October 27, 2004 04:20 PMYou ain't kidding about that nasty crash. Of course I updated about 1 minute before your post :(
Posted by: Chris G. on October 27, 2004 04:22 PMkwanbis, what version were you upgrading from and did you have extensions installed?
--Asa
Posted by: Asa Dotzler on October 27, 2004 04:30 PMASA, You got msn?
Posted by: XeroCool on October 27, 2004 04:32 PMAsa,
FYI:
I followed the update instructions and did not receieve the crash. I was upgrading from yesterday's nightly (Oct 26), and I have Weatherfox, BBCode, Spellbound, Adblock, and Web Developer installed.
yes i do, kwanbis hotmail com ... i don't remember what version i was updating from ... but i think it was PR1 ... is there a place where i can check? IE View 0.7, bookmark backup 0.3, open book 1.0, flashgot 0.4, webmailcompose 0.5.6
Posted by: kwanbis on October 27, 2004 04:57 PMI'm not sure if this is a bug or not, but my open-external-links-in-new-windows option didn't seem to migrate. I was able to find the UI to fix it, but would that classify as some sort of regression?
Posted by: David Schontzler on October 27, 2004 05:06 PMNo problems on first look.
Although I still would love to see a fix for https://bugzilla.mozilla.org/show_bug.cgi?id=251862 (Find toolbar - highlight freezes), because this can totally freeze FF up to a minute even on state-of-the-art machines easily. Not a 'minor' bug in my eyes.
I hope to see localized DE builds soon, there hasnt been anything official german since 0.9.3. Difficult to promote the quick security responses if localized builds are three months behind.
Posted by: Udo on October 27, 2004 05:07 PM[off-topic]
Asa,
What would Mo do without you. You are great !!
Posted by: z on October 27, 2004 05:13 PMHow about putting up some "official" BitTorrents for FirefoxSetup.exe?
Come Nov 9, Mozilla servers will be hard-pressed and that way, we can save some bandwidth for new users?
Posted by: [another off-topic] on October 27, 2004 05:19 PMQuick comment: The User Agent string doesn't fit in the About box. It either needs more room or needs to be a smaller font size.
RC1 on XP w/SP2. I've bumped up my Windows Message Box text size to 9 (default is 8), which may have something to do with it.
Posted by: David Schontzler on October 27, 2004 05:26 PMbittorrents are mostly worthless for Firefox. the downloads are so small that it just doesn't make it worth it. when we did offer bittorrents, they accounted for only a tiny fraction of our total downloads. bittorrent is ideal for large files and just doesn't help much with a 4.5MB download.
--Asa
Posted by: Asa Dotzler on October 27, 2004 06:16 PMI don't know if this is would be considered a regressed bug, because I'm not sure that it was filed correctly in the first place (and not knowing, I've been loath to change its particulars).
https://bugzilla.mozilla.org/show_bug.cgi?id=257288
It's listed as a trunk bug, but RC1 is a branch/aviary build, right? This bug cropped up between .9.3 and PR1. It's terribly annoying, but I don't know that the developers would consider it showstopping.
Been using PC1 since this afternoon. All my extensions still work, and things are going nicely.
Great work!
Posted by: Michael Venables on October 27, 2004 09:05 PM:-( No one answered my question in my previous comment, so I filed the bug anyway...
Posted by: minghong on October 27, 2004 09:42 PMI don't think many people ever knew about the torrents. I personally think it would be a good idea to have torrents for the FF1.0 release.
Posted by: Joergen Ramskov on October 27, 2004 11:27 PMI uninstalled my nightly build and installed RC1, i noticed that the red critical update button was still there. The one about upgrading to 0.10.1
I made it go away by clicking on it, having Firefox search for the update. It didnt, so the button is now gone.
dont know whough if this happends only when upgrading from nightly builds or from Preview Release as well.
Posted by: José Jeria on October 28, 2004 12:11 AMThat hasn't happened for me for quite a long time. I used to have to click on the red update icon every day with each new nightly build for weeks but I haven't had to do it recently. Did you upgrade to 0.10.1 when it came out originally?
Posted by: Chris Blore on October 28, 2004 01:05 AMNo, my userAgent said 0.10. I never downloaded 0.10.1 since the nightly builds had that fix.
Posted by: José Jeria on October 28, 2004 03:15 AMMaybe you should add Ability to Sort Bookmarks to the features list Asa.
Right-click on the bookmark menu and pick "sort by name".
Posted by: Jugalator on October 28, 2004 07:50 AMSorry, misunderstood your message... I'm tired :-(
Posted by: Jugalator on October 28, 2004 07:51 AMwww.mozilla.org/mirrors.html looks very strange
I've put a screen shot at www.schachbezirk-freiburg.de/strange-rendering.png
UA:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Update from 0.10.1 didn't work (XML-error message after the download)
Posted by: w_j_s on October 28, 2004 11:13 AMWe're promoting Firefox as the browser with "tabbed browsing". Every article we
wrote, every user we try to convince we tell him: "hey, Firefox has got tabbed
browsing". So he install it, and what he will say?
- "Where is that "tabbed browsing" they talk so often about?"
If it's a fabolous feature, why we hide it? See just what Opera had done. I
think a small "new tab" button it's useful to new and old users. Geek could
remove it, but please keep in mind we're approaching average users. We've a "go"
button beside the location bar (I think also IE users knows the keyboard Return
function), and we don't have an icon for that wonderfull new feature for whom
Firefox is famous for. Without the explicit button tabbed browsing is complicated and unusable for most users, we've a "close" button in the default layout but not an "open" one.
This is the bug I submitted today and has been set as duplicate of a WONTFIX bug
https://bugzilla.mozilla.org/show_bug.cgi?id=186865
I think it's really strange l10n builds are occuring for the first time in the RC phase. I'm seeing an awful lot of glitches (wrong accellerators, untranslated strings, single characters instead of entire words, XUL errors in about box) in the nl-NL.
But I wasn't going to recommend the nl-NL anyway since the translation is really way overdone, making things like website sound like "web hide-out" (webstek in Dutch) and browser like "flipping-pages tool" (bladerprogramma) while keeping things like "Plug-ins" which is exactly the opposite of the Dutch Microsoft translations (which keeps things like website and browser but calls plug-ins "invoegtoepassingen").
In short: I will be ashamed if the Mozilla Foundation releases such a nl-NL release even though I'm enjoying a dutch operating system.
Posted by: Bram van Leur on October 28, 2004 01:53 PMBram: this is not a problem made by mozilla.org, but by the dutch translation team.
French version is - as far as I know - awfully broken about some shortcuts.
So shout on translation team, not on mozilla.org coders :)
Posted by: FredB on October 28, 2004 02:51 PM(quote)# Single window mode (load all pop-ups in new tabs,) set in the Advanced panel of the browser Options/Preferences window.(end quote)
This should be changed to work the way the TBP Lite extension did. That extension could tell the diff between a "window" and a popup.
Please see http://forums.mozillazine.org/viewtopic.php?t=145739
Posted by: Neil Parks on October 28, 2004 03:00 PM(quoting me)This should be changed to work the way the TBP Lite extension did.(end quote)
I should have added, "by default". As the forum discussion shows, there are tweaks that can be made in about:config. But such tweaking should not be necessary.
>www.mozilla.org/mirrors.html looks very strange
>
>I've put a screen shot at www.schachbezirk-freiburg.de/strange-rendering.png
>
>UA:
>Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
>
>Update from 0.10.1 didn't work (XML-error message after the download)
It renders the same here
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041028 Firefox/1.0RC1
FIND and FIND AGAIN Function
I am using
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041028 Firefox/1.0RC1
on WinXP
The Problem......
If you now right click a page and "view source" you can no longer use the FIND or FIND AGAIN functions with this build.
John: That worksforme, also on XP. No extensions installed, default theme.
Posted by: José Jeria on October 29, 2004 07:45 AMThe "Sort by name" feature in RC1 is broken. Another regression, folks...
Posted by: Muricio on October 31, 2004 12:02 PMI am so ashamed of the mozilla.org at the momment... your no longer going have a mac os 1.0... your just going to push all builds at the same time... while the os x builds are good... they have a lot of polish to make the 1.0 quality.. many things are still broken... and they NEED to be fixed will they by the time 1.0 rolls around in less than a week?
Posted by: si on October 31, 2004 06:58 PM> Gecko and website rendering -- we took a few significant layout/css fixes.
I *really* would like to see bug 163545 fixed - there's a testcase and image examples attached of how the problem manifests itself, it seemed to have been fixed in an earlier build of Mozilla but is still present in FF 1.0RC2.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
This bug makes FF unusable with my companies site, which is a real bummer - I've been telling people it will be fixed in FF 1.0 as it seemed to have been squashed in the earlier Mozilla build.
Is there any hope of this being fixed in 1.0?
Posted by: Neil on November 4, 2004 03:59 PM