Isn't this one
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-aviary1.0.1/
more likely to have the latest check-in (2005-05-09 19:11)? I don't know how the clocks work in relation to the file times of the builds.

Anything particular we should be testing?

I don't seem to be able to install new extensions by dragging from the desktop to the Extensions Manager window. Can anyone else confirm this?

Confirmed on:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4

The above was with a clean profile. I also noticed I cannot install themes by dragging and dropping onto the theme window. This begs the question, why hasn't some install theme/extension buttons been put in by now? Sorry if I'm bringing the discussion off-topic.

The extension install (and theme install) drag and drop issue is actually fixed. I linked the wrong builds. Sorry. Correct builds are now linked.

- A

Yes, themes and extensions can install by dragging and dropping them over their corresponding windows or the main Firefox browser window in the new build you linked. Do you have a site where we can test the exploits from 1.0.3 (without doing any harm to our machines, of course)?

Drag and drop extensions from the desktop to the Extension Manager still crashes FF, under Linux. Known problem, see
bug:269568

In 1.0.3 the options window was with horizontal icons and some options changed (for good)
This version has the old fashined options...

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4

Er, no, that's a trunk-only change, you must be mistaken...

1. AFAICT, mozillahappy is right in saying that http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-aviary1.0.1/ (and its most diligent mirrors) is more likely to hold the latest version for all 3 platforms, since it's supposed to "update itself" to show the latest aviary builds at any point in time.

2. I've been using every Fx nightly since they were still calling themselves "1.0.3" and I haven't noticed any new bugs yet. I'm a happy man. :-)

Daniel: there are 2 ways to test the IconURL part of the exploit at Bug 293302

After some tests, all works perfectly!

IS this the latest build, as my UA string shows:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050510 Firefox/1.0.4

Which is the latest Aviary here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-aviary1.0.1/

???

Slightly OT, but "begging the question" is simply a way of saying "circular reasoning," or assuming the very point you're trying to prove (like "IE is better than Firefox because it's better" ... though that's a terribly obvious example). See http://en.wikipedia.org/wiki/Beg_the_question

Starting in the 90's, usage has kinda been changing, but it's still frowned upon. It begs one to *ask* the question, or it *raises* the question, but by the true definition (a translated phrase of Latin, if I remember), it does not *beg* the question.

I've installed 1.0.4 and upon starting firefox, nothing will load. I cannot click anything but the X to close the window. Im guessing this is from an extension but im not sure. Ive done an install with no extentions and it worked. I had these extentions when it did not work.

-ieview0.87
-Forecast Fox 0.71
-A's Yahoo mail notifier 0.6
-Stockticker 0.5.2
-ReloadEvery 0.5
-DictionarySearch 0.9.2
-My IP Tool 0.1.6
-Download Manager Tweak 0.6.5
-Search Button 0.4.8
-Adblock 0.5.2.039

I'm going to hold off installing anything until there's clarity about which damn build is the candidate. Here's a hint - call the directory aviary1.0.4-candidates :)

Hi! I did the IconURL test with the new build after adding the site to my whitelist. Clicking on the link did nothing (AFAIK). Is that a good thing? By the way, the install sofware info bar doesn't have an X (close) button. Is there a bug I can vote for? Thanks!

Mark -- calling it aviary1.0.4 would be incorrect because that would mean it was a new branch, rather than a continuation of the feature-frozen bugfix-only branch that began with 1.0.1... right?

Using the version from the corrected links:
- using the old profile imported from 1.03 (some themes and 11 extensions) works fine
- no problem installing extensions on a fresh profile either

At first glance everything runs smoothly but I'll keep testing.

Just install Firefox 1.0.4. No issues

[quote]
Slightly OT, but "begging the question" is simply a way of saying "circular reasoning," or assuming the very point you're trying to prove (like "IE is better than Firefox because it's better" ... though that's a terribly obvious example). See http://en.wikipedia.org/wiki/Beg_the_question

Starting in the 90's, usage has kinda been changing, but it's still frowned upon. It begs one to *ask* the question, or it *raises* the question, but by the true definition (a translated phrase of Latin, if I remember), it does not *beg* the question.
[/quote]

Don't make me post a link to the definition of "slightly."

This build seems to be working fine.

I've installed 1.0.4 and upon starting firefox, nothing will load. I cannot click anything but the X to close the window. Im guessing this is from an extension but im not sure. Ive done an install with no extentions and it worked. I had these extentions when it did not work.

Something similar happened to me - same symptoms - after ugrading some extensions recently under 1.02. The extensions I have in common to yours are: IEview and Download Manager Tweak.

Upgrading to 1.03 didn't solve the problem, but _sometimes_ FF works (if called with an url), altough I can't open links in the same page or in new windows (via left click, via menu or popup menu), only open links in new tabs.

Is this fix going to be checked into the trunk or just the branch?

Er, no, that's a trunk-only change, you must be mistaken...

errr
ok, this is not a trunk build
I'm a little twisted with this...
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4

That aswer my second question about svg not showing...

Whats new in this versions..??

Yes, I realize that this is not a trunk build. That's why I'm asking whether trunk testers will need to switch to a branch build to get this fix.

I know this question keeps being asked, but I don't hear a clear answer yet.

You want everyone to test the one attached to the link at the top of this thread, which for the Mac is:
firefox-1.0.4.en-US.mac.dmg 09-May-2005 23:30 8.7M

Yesterday's -- right? So everyone is testing the same May 9th build?

Not the one found in
/pub/mozilla.org/firefox/nightly/latest-aviary1.0.1
(which is going to be different -- depending on when and what mirror are used - hourly or daily).

Right?

Cue sound of one hand clapping -- against forehead: "Duh."

Okay, the linked Mac build May 9th says "no mountable file system" when doubleclicked. Off to try today's irregardless.

Just to say, I'm currently using the 2005-05-10-16-aviary1.0.1 nightly (on Linux ;) ), and I haven't noticed any problems. It runs perfectly fine. I haven't been doing too much, but it *is* running fine with all my extensions and all, so that's a good thing..

Hmm...
This Rc seemed to work very well for the first few hours. Then it seems
that this build broke my back and forward buttons on my Logitech MX1000.
After reverting back to 1.0.3 everything works fine again.

I'm using the latest aviary build. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050510 Firefox/1.0.4

The only problem I've found so far is that in the bookmarks toolbar, the normal behavior when right clicking on a bookmark is the options menu to appear (open, open in new window, one in new tab, etc). Instead I see a tiny little box with nothing inside of it. In the Javascript Console I receive the following errors:

Error: document.getElementById("bookmarks-chevron") has no properties
Source File: chrome://browser/content/bookmarks/bookmarksMenu.js
Line: 657

Error: bt has no properties
Source File: chrome://browser/content/bookmarks/bookmarksMenu.js
Line: 145

Hope this helps.

I've installed Gecko/20050509 Firefox/1.0.4 on my Debian Sarge (2.6.8-2-386) box. The install went normally and everything seems to work as it did before. Sorry to be thick but does this release resolve the 2 security issues?

According to the front page of mozillazine.org this should resolve the 2 security issues

I've installed 1.0.4 rc and it's working just fine. One of the extensions I have is IEview and it still works.

There are some problems using Gmail with the new version.

Tested Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4 (WinXP, SP2, fully patched)
No problems with FF, only Aardvark extension has some minor flaws...
Great job!

Tested Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4.
This build has a lesser support of SVG than the previous ( rv:1.8b2) Gecko/20050507 Firefox/1.0+.
Seems to have problems with the tag, the SVGDom and events attributes.
The comparison between this two builds can be done with the samples of "http://www.croczilla.com/svg/samples/" or the examples accompanying the Batik toolkit. For those related to the subset of SVG 1.1 supposed to be implemented in Firefox, of course.
Yet a great job in the meantime and in the way to FX 2.

Ornithornyque: that's because SVG is only supported on the TRUNK builds (1.8b2/1.0+), while this is an aviary build (1.7.8/1.0.4)

Seems to be working fine, with all 7 extensions (at least they don't crash). Well done! Being fast to respond to security flaws is critical for FF.

As a totally new installation it imports bookmarks and internet settings from IE and windows. But the homepage seems to be hijacked by the google/ffx start page rather than importing the IE homepage setting - EVEN when the check box is unchecked during installation.

It really shouldn't even be checked by default.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4

Works fine at my job: WinXP Pro SP2, ZoneAlarm Firewall
Extensions:
Adblock
WebDeveloper
Autocopy

Still testing at home PC...

Hi guys,
as someone who ran a few updates on 1.0.3 BEFORE I heard the news, but after it actually broke - I'm somewhat concerned. If I am indeed open to the exploit, or if my security has been compromised, how would I know? Could I do something about it? I've already disabled JavaScript --- but if I've been compromised, I should be doing other things, right?
The thing that scared me is that I ran an autoupdate because it said that a Walnut Skin was available in a newer version ... but there were two of those (identical) radio boxes on the update panel.
Comments, please?
Fear and Terror,
AK

All test and Installed extensions working OK
No problems found to date.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050509 Firefox/1.0.4

Extensions Installed:
ChatZilla 0.9.68a
googlebar 0.9.5.06
fireftp 0.88
Mozilla Calendar 0.8.3+
WebMailCompose 0.6.1

I've noticed with the 20050510 release candidate that dialogs are horrendously slow - clicking any button which dismisses the dialog causes Firefox to pause for up to five or six seconds before finally closing the dialog.

I just downloaded and installed Firefox 1.0.4 with bad results. I totally lost my ability to find my home page (Yahoo) and was not able to browse at all. Not even my bookmarks. Everything came up as "not able to find". I had to do a system restore back to yesterday (May 10) and all is now back in running order using 1.0.3 I might point out that my other browser (I hate to even say it, (Internet Explorer), still worked, so it was not a loss of my internet connection. I have been using Firefox for about 4 months and love it. I will keep following the progress on this 1.0 4.and hope what ever bug hit me will be corrected.
Keep up the good work.

See my posting above at 03:42 PM

In addition to the above problems. I just discovered that when I attempted to do internet banking, I found that I am unable to do any banking using Firefox as a browser because the bank requires that java script has to be enabled. Naturally, I followed your advice and disabled java script using your suggested work around. Prior to going back to 1.0.3.by using system restore, I uninstalled 1.0.4. Now, when I go to Help and check "about" it says I am using 1.0.4.even though it as been uninstalled. Hopefully this will all be resolved in the next day or two, but in the meantime, I will have to use Internet Explorer to do my banking.

Nit: On the last FireFox screen, the bottom says "Click Next to Continue", but the button actually says "Install" not "Next".

Cannot install theme, suspect other problem but cannot reproduce

Hey i cant even get the extension box up? and when i mnanuially install extensions it doesnt do anythting?

I've posted a comment before about firefox 1.02 not reacting to any UI interaction after upgrading some extensions. In that post I suspected ieview or download manager tweak to be the culprit, based on the extensions a previous poster had in common.
Altough I could run in FF safe-mode, that didn't allow to disable extensions! (When will that be fixed?!)
I have since found what the offending extensions where, and how to fix (well, disable) them. ***This should be documented!****

Here are the steps to allow you to selectively disable the extensions:
You'll need to open the firefox application passing it some additional info (command-line parameters). In order to do so, go to the Firefox shortcut you usually use to launch, be it in the desktop, the start menu, or the quicklaunch bar, and right-click. Select 'copy' and then 'paste' a copy in an convenient location. I sugest you create 3 copies, and rename them to "Firefox - With Console", "Firefox - Profile Selector" and "Firefox - Extensions Manager".
Now, right-click on each of the newly-created shortcut (one at a time!), select properties. In the first field, after the path to the executable ("c:\Programs\Mozilla Firefox\Firefox.exe" or something similar - if it isn't surrounded by quotes, YOU'LL NEED TO ADD THESE) append the following WITHOUT THE QUOTES: " -console". In the other shortcuts, do the same, but append " -p" for the second and " -chrome chrome://mozapp/content/extensions/extensions.xul?type=extensions" for the third.
Close the properties page, or leave that open and just click 'apply'.

Of course, if you know what shortcuts and command-line parameters are you might as well do it in other ways...

Now, when you open the first shortcut, you'll see a console (black 'dos' window) with some text. That is by virtue of the -console command-line parameter. It allows you to find out what firefox might be complaining about.

The second shortcut lets you choose or add a profile. You probably only have one, but you might need to create a new empty one if you get the default one messed up. Also, you can (not so easily) find out where your current profile data is stored, in order to do a back-up.

Finally, the shortcut with the -chrome parameter instructs firefox to bring up the extensions window and not the browser window, so you will get a chance at changing your installed extensions - disable them by right-clicking and selecting the 'disable' option. You might also alter the loading order, or try to update them, but then that is also possible in safe-mode.

That was how I solved my problem. I had to disable the Slogger 0.5.11 and the User Agent Switcher 0.6.6 extensions (I hope the problems with these extensions get fixed), and now everything seems to work fine again.

***
Firefox is great, I really appreciate the work the mofo has been doing. I have supported ff for almost a year, but now I have to admit it is still very immature. This kind of 'hacks' is perfect for Mozilla, but unnacceptable for Firefox.

You can choose any 4 search engines and the screen will divide your browser into 4 windows displaying each of the search engine results.

"Connection refused" error seems to be fixed!! I've been plagued by this error for some time in all its worst manifestations (pinging still works, DNS still works, but once you get the error all browsing -- even with IE -- is finished until an XPPro reboot). Tried all the tweaks, proxy, winsock and stack rebuilds, prefs.js and registry fixes. Nada works. But so far - a few days now and it used to surface after 5-10 minutes -- I have not experienced the error with 1.04.