We found a problem (thanks Martijn!!) in the first round of candidates and this new round of builds corrects that problem. Any help testing these new builds is greatly appreciated.
Posted by asa at April 3, 2005 10:54 AMWhat is exactly changed from 1.0.2 and 1.0.3 (besides the installer)?
P.S. Someone should update the roadmap as it is getting pretty outdated. :-P
Posted by: minghong on April 3, 2005 12:27 PMDoes this build have the fix for the memory problem where FF does not release memory of closed tabs? Quite a crippling bug...glad to hear it was fixed, but no details of when it will be in build???
Posted by: Eddie on April 3, 2005 01:13 PMShould i install this build over release candidate 1 or do a clean install of release candidate 2?
Posted by: xrayspex on April 3, 2005 01:36 PMHey, the file name of the installer is incorrect. It gives the version number as 2.0.3.
Posted by: Rishi M on April 3, 2005 01:36 PMExcuse the double post, but the new 1.0.3RC installer created a startup registry entry. What for?
Posted by: Rishi M on April 3, 2005 01:46 PMRishi: That's a bug in the Firefox download manager, not a problem with the filename. See bug 231048.
Posted by: Gavin Sharp on April 3, 2005 01:59 PMRishi, i have no placed start up registry entry for FF afer installing this build.
Posted by: Xrayspex on April 3, 2005 02:01 PMHi Asa
This update works nicely, thanks.
PS I know this is out of place, but I was wondering if you could press to fix bug 202251. Basically, if you type an unaccented version of a word in the Find as you Type it doesn't highlight any accented versions. This is very annoying for those of us who are multilingual!
Posted by: poynting on April 3, 2005 02:09 PMHello, Asa!
There is a regression bug (287459) in 1.0.2, which has a patch waiting for approval 1.0.3, I've e-mailed to drivers yesterday, but I don't recieved any answers so I'll write here.
Thank you.
Posted by: ANBO Motohiko on April 3, 2005 02:51 PMOops, posted this in the wrong thread first.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050403 Firefox/1.0.3
OSX: Near as I can tell this is what's happening when I open FF 1.0.3, today's OSX build, then open new windows -- four, one after another.
FF Looks in 2 directories for a plugin, fails; each time it tries to download the plugin, fails; it stumbles over something that's been deprecated, then OSX tries to write a crash log and crashes the Console application (Firefox stays open).
Log:
/Applications/Firefox.app/Contents/MacOS/firefox-bin: can't map file: /Applications/Firefox.app/Contents/MacOS/plugins/Default Plugin.plugin ((os/kern) invalid argument)
/Applications/Firefox.app/Contents/MacOS/firefox-bin: can't map file: /Library/Internet Plug-Ins/MRJPlugin.plugin ((os/kern) invalid argument)
### MRJPlugin: getPluginBundle() here. ###
### MRJPlugin: CFBundleGetBundleWithIdentifier() succeeded. ###
### MRJPlugin: CFURLGetFSRef() succeeded. ###
*** loading the extensions datasource
/Applications/Firefox.app/Contents/MacOS/firefox-bin: can't map file: /Library/Internet Plug-Ins/MRJPlugin.plugin ((os/kern) invalid argument)
### MRJPlugin: getPluginBundle() here. ###
### MRJPlugin: CFBundleGetBundleWithIdentifier() succeeded. ###
### MRJPlugin: CFURLGetFSRef() succeeded. ###
*** loading the extensions datasource
Apr 3 14:35:15 Hank /Applications/Firefox.app/Contents/MacOS/firefox-bin: *** Warning: ATSUMeasureText has been deprecated. Use ATSUGetUnjustifiedBounds instead. ***
Apr 3 14:35:19 Hank crashdump: Started writing crash report to: /Users/hank/Library/Logs/CrashReporter/Console.crash.log
Apr 3 14:35:20 Hank crashdump: Finished writing crash report to: /Users/hank/Library/Logs/CrashReporter/Console.crash.log
Posted by: Hank Roberts on April 3, 2005 02:56 PMThanks for the info, Gavin. :-)
Although Spybot S&D told me that a startup registry entry had been added for 'firefox.exe', the System Configuration Utility shows no such entry. That's odd.
Posted by: Rishi M on April 3, 2005 03:02 PMEddie: no, this won't have a fix for the memory issue - that'll be in 1.1. As far as I know, the installer bug leaving behind old versions in the uninstall list, and a couple of security issues, are all that's changed from 1.0.2 to 1.0.3 so far.
Posted by: michaell on April 3, 2005 03:04 PMCopy and paste with OSX FF 1.0.3 (today's build) seem very messed up -- sometimes only the menu but not the mouse works; consistently it's possible to copy to an outside text file with the menus but not drag with the mouse; it's never possible to copy and paste from one Firefox tab or window to another for me with either mouse or menus.
I am able to pull down the About menu, hilight this, command-C, click here and command-V:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050403 Firefox/1.0.3
Not sure if this is just 1.0.3 or is a known bug, but
-- for links (hilighted and recognized by FF
-- within windows like this one: javascript:HaloScan('111219934082864627');
(which are used inside web pages, as here: http://preposterousuniverse.blogspot.com/2005_03_01_preposterousuniverse_archive.html#111155024666490546)
-- right click on a link and 'Open as new...' does nothing at all.
Posted by: Hank Roberts on April 3, 2005 07:40 PMThe links to the release notes (both in about: and in Firefox Help) point to the 1.0 notes instead of the 1.0.3 notes (which don't exist yet, but they point to the 1.0 URL). This is also a problem in 1.0.2, and probably 1.0.1. See bug 288864.
Posted by: Tom Hessman on April 3, 2005 11:20 PMHeh :) I didn't know it was also checked into the Aviary build.
I only keep track of trunk builds. That swallows enough time already, and the Aviary builds are too boring for me anyway.
Does prompt(); still return an error? It didn't in 1.0 and some extensions need it.
Posted by: Anonymous on April 4, 2005 05:02 AMI have FF set to download all files to the Desktop, but when I go to download a file the Save As dialog always pops up instead of just saving the file to the Desktop.
Anyone else see this problem with FF 1.0.3 RC2 ?
Posted by: Defenestration on April 4, 2005 06:09 AMI chose the FF 1.0.3 april 2nd aviary zip. I had been using versions of ff from 9.0 to most recently 1.0.2 posted march 30th, usually with no problems. I am using windows xp professional and had no problem with macromedia shockwave on any previous version, I do full unistalls and reinstall each item (flashplayer, shockwave, etc.) each time resulting with no problems.
But, with the FF 1.0.3 rc1 april 2nd aviary zip. I can't get shockwave to work in ff. I uninstalled it and reinstalled it and it will work in IE, but not ff. I saw some of the old bug posting for such problems, but I am not going to do anything manually to the registry, we shouldn't have to. Please repair this problem or post a work around that does not require messing with the registry.
Everything is still working fine .. no problems with the installation
Would using a profile backup utility be out of the testing scope for what we're doing here?
Posted by: John Blanton on April 4, 2005 09:11 AMpillpusher,
Use the MacroMedia Uninstaller packages available at (http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_14157) and/or full/manual registry search/delete! You may wish to use FlashBlock extension in the future!
Well this is weird, I've tried the last 3 Linux Aviary 1.0.3 tar.gz nightly builds. I always rename my old firefox browser folder so it untars it into a fresh folder (and I have a copy if something doesn't work.), and not one of the nightly builds will work using my current profile. They start up, but all I get are the browser buttons, and that's it. None of the menu commands work no web pages come up, nada. So, after I clicked on the X in the top right a number of times so I coukd get the Timed out error box to stop FF, I tried renaming my profile folder in .mozilla so FF 1.0.3 would have to create a new one.
Okay, I have a browser again (minus all my extensions). I then start re-installing the ones I use, and the first one I tried (If I remember right it was image zoom) caused the same problem when I restarted the browser. In fact, it didn't matter WHAT extension I tried. Delete profile, restart browser, it works, install an extension, browser dies.
If it helps, the last one I tried (before giving up and going back to the latest trunk branch ^_^) was: firefox-1.0.3.en-US.linux-i686.tar.gz 05-Apr-2005 21:01 7.9M .
Really weird, as previously I never had problems installing the Aviary builds.
Hope someone knows what's going on here?
Posted by: SantaFe on April 6, 2005 01:30 PMHI
Testing Version 1.0.3. Clean Install. I am having an issue with Links. If i try To click on a link sometimes it works other times it Does not. Never know what will work. Links highlight as they should.
Posted by: Black knight on April 9, 2005 04:24 AMJust Found my problem. It appears that the links are actually working, But the Popup Blocker is stopping them. Never had this issue with Older versions. the site s Question today is Dell outlet. Had issues with others, but Never thought to check the popup Blocker.
BK
Posted by: Black Knight on April 9, 2005 04:37 AMMozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050410 Firefox/1.0.3
(I'm picking the latest daily out of the Nightly/Aviary 1.0.1 folder --- hoping that's the right place to look. I'm in a maze of twisty little links, and can't tell if they're all alike or not!)
It's odd -- slower than usual, still can't reliably copy and paste using command-C, command-V nor the menus. Can't drag a selection between Firefox windows at all, it's simply ignored (the previous selection is still in the buffer).
But I can copy and paste OR drag to a text file, and from that copy and paste or drag to a different Firefox window, reliably.
Posted by: Hank Roberts on April 11, 2005 05:42 AMOh, and this is why I'm confused about what Asa actually wants tested:
The link at the top of this thread, which people are asked to test, is:
So -- it's dated April 3.
Now, would that be the same as the April 10th build I found and am using?
What do you want tested?
Posted by: Hank Roberts on April 11, 2005 05:44 AM