Just to be absolutely clear, this is the Firefox Preview Release, not Firefox 1.0. (Sometimes you gotta shout or they won't hear.)
Looks like we're getting some good advertising for this testing release. We'll probably get a decent little flood of new bug reports and comments at slashdot and around the blogosphere. If you all want to help out with a bit more than just testing the builds yourself, please check out what others are saying and if you see something that looks bad, help us find out by either convincing them to file bugs, of filing or finding and nominating the bugs.
I try to keep my eye on all the feedback but it looks from the trackbacks at my blog alone, like there's going to be more of this feedback than I can handle myself. Any help you all can give in gathering up any valuable feedback and getting it in front of our eyes, would be great.
Posted by asa at September 12, 2004 08:47 AMYou guys are doing some great work. Keep it up.
Posted by: James Willock on September 12, 2004 10:10 AM> let's just call it 0.10
Only if firefox 1.0 preview will be called 0.11
Synonymous, thanks for pointing out my error. I meant to say "let's just call it 0.10rc" since that's a lot easier than "Mozilla Firefox 1.0 Preview Release, Release Candidate". I've corrected the title of the post.
--Asa
Posted by: Asa Dotzler on September 12, 2004 10:45 AMWell, I'm working on it. I've found a bug so far. And I'm working on making it easier for endusers to report bugs.
Posted by: Robert Accettura on September 12, 2004 11:37 AMThe actual .exe is still versioned as 0.9, not 0.10. Other than that, everything seems good here!
Posted by: Doug on September 12, 2004 11:48 AMI'm sure these must both be filed as a bugs already, but I can't find them.
I have installed both DOM Inspector and Talkback. But upon checking for updates, I am prompted to install both of these optional components, despite already having them!
Also upon updating to a newer version of an extension, I wasn't prompted to restart the browser so the new version could take effect.
Posted by: Doug on September 12, 2004 12:38 PMBut of course Slahdotters are still complaining for not yet fixed on Aviary bug #217527 (famous Slashdot rendering bug). And if I understand Bugzilla correctly it won't be fixed in 1.0 (blocking status was denied). I hope it will be moved from Trunk before 1.0 will be released.
Posted by: Pshemekan on September 12, 2004 12:50 PMUpdate from 0.93 release was flawless for me (about 2 hours ago).
Just saw the automatic extension update kick in - GooglePreview was disabled during the update, it was just updated and I got a notification telling me it had been installed.
Neat.
Pshemekan: If the slashdotters want that fix, they have to fix the regression the patch causes.
Posted by: Quark on September 12, 2004 02:23 PMWhen I view windows media it shows at 6.2 not 9 which is installed on my computer.
http://poststuff2.entensity.net/091004/media.php?media=woody.wmv
Posted by: sdfsf on September 12, 2004 02:54 PMI have problems with bookmarks, I can't open subfolder....
Posted by: Mine on September 13, 2004 10:04 AM