zarro boogs 'n 1.5 rc1 just around the corner
Today we bounced off of zarro boogs for the Firefox 1.5 release candidate. If all goes well, the builds we created last night will be the builds we ship as RC1 sometime early next week (I think we're looking at Wednesday.)
Unless we find stop-ship problems in the feedback from the release candidate, these builds will become Firefox 1.5 -- though I can't think of a time when the widespread testing we get in a release candidate did not turn up new issues. The point is that we're down to no known blockers and that means it's time to package up the builds, get the localizations all signed off on, make one final QA sweep, and ship this thing.
If you find bugs that should block the release of Firefox 1.5, please let us know by reporting the bug, nominating it with the blocking1.8rc1? flag, and letting me know here in the comments.
You can find our test builds here:
reactions, thoughts, comments, etc.
Zarro Blockers? The AMO bug isn't a blocker anymore? https://bugzilla.mozilla.org/show_bug.cgi?id=304857
Posted by: amano | October 26, 2005 1:06 PM
So far win 1.5 test is working smooth here :)
Posted by: Xrayspex | October 26, 2005 1:17 PM
@amano: that bug has nothing to do with the firefox code. its a website problem.
Posted by: ColdFusion650 | October 26, 2005 1:28 PM
So far today's Mac Build 2005102603 has been working perfectly for 9 hours now. Pure fun, thanks a lot!!
Dex
Posted by: dex_sf | October 26, 2005 1:35 PM
Ahm, Asa, the Mac Build 2005102519 you're linking to still had problems with the Phantom Scrollbars, not a good idea to use it as test release for RC1. In Mac Build 2005102603 that pretty obvious problem doesn't turn up anymore.
Dex
Posted by: dex_sf | October 26, 2005 1:41 PM
If we downloaded Fx 1.5b2 (and we're presumably on the "beta" channel), will we be notified to upgrade to 1.5RC1? If we decline to upgrade to RC1, will be be able to upgrade from 1.5b2 to 1.5 or will we be forced to take the route from 1.5b2 -> 1.5RC1 -> 1.5?
I'm asking because of the people's computers I've installed this on. My mother is still running on 1.0.7 because of extension compatibility issues and because she needs to take change slowly. My friend is a little more technical, just by the generation she grew up in, but she is one of those (lots) of people that never update her software. I installed 1.5b2 on her computer so that she'll be more agressively influenced to take an upgrade path herself, and I'm just wondering what kind of experiences these two Regular People ;) (and myself) are in for.
Thanks!
Posted by: Simplex | October 26, 2005 1:47 PM
I nominated https://bugzilla.mozilla.org/show_bug.cgi?id=313422 for a thunderbird blocking bug. The RSS reader is not useful any longer for me because some feeds do not work any more.
Tobias
Posted by: Tobias | October 26, 2005 1:49 PM
Is it just me, or is the URLbar still broken? Right now I have 5 tabs. If I ctrl-pgup/pgdn through them, all but one show this blog post's URL as the URL of the tab. Basically, right now, the first three tabs' URLbars are broken. They show the URL of whatever newer (tabs 4 theough x) tab was up there before. Tab 6 now has Google.com, so the first three show that if I switch to them, etc. Basically, there just seems to eb massive URLbar breakage. Makes copying URLs hard.
Posted by: Grey Hodge | October 26, 2005 2:32 PM
I'm feeling a little uneasy about a Gecko bug that wasn't there previously:
https://bugzilla.mozilla.org/show_bug.cgi?id=312777
http://www.fu2k.org/alex/css/bugs/gecko1.8b2+_negativefloats/
Also mentioned on:
http://www.positioniseverything.net/articles/onetruelayout/
I suppose this could break sites that have been working in Firefox until now? Shouldn't this be considered a blocker, then?
Posted by: Jerome Dahdah | October 26, 2005 2:44 PM
Ignore me, this is probably an extension.
Posted by: Grey Hodge | October 26, 2005 2:45 PM
Unfortunately, the Find bar is giving incorrect search results with tabs. Bugs 313653 and 313657. It's a pain in the neck if you try to search multiple tabs, but I'll leave it to you to decide if it's a blocker.
Posted by: VanillaMozilla | October 26, 2005 3:27 PM
Hmm, this build seems slower than B2.
Also, I still want 283697 to be fixed. :|
Posted by: Manuzhai | October 26, 2005 4:08 PM
It seems especially slow when first starting up (I mostly keep my browser open day after day, only restart it occasionally or when it crashes) with a bunch of tabs already open (courtesy of the SessionSaver extension).
Posted by: Manuzhai | October 26, 2005 4:13 PM
This RC1 test is slower and some of the extentions don't work for instance, google, I don't think, it is normal. The tab fuction is also having problems as it does not open new tabs instead it opens new windows.
Posted by: alberto | October 26, 2005 5:21 PM
I would consider https://bugzilla.mozilla.org/show_bug.cgi?id=313220 a pretty bad bug, but then I'm a Greasemonkey programmer. The comments on this entry have put me off from testing 1.5rc1, so I don't know whether the bug still occurs there. Can someone test and confirm or close the bug?
Posted by: Matthias 'moeffju' Bauer | October 26, 2005 5:34 PM
Though this may be a known problem, I found that the "Read Mail" menu (Tools -> Read Mail) showed incorrect notification. It says I have 17 new mails, while I have no unread mails as a matter of fact. My default mailer is not Thunderbird ;-) I use it as a RSS reader :-)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 ID:2005102519
Posted by: End User | October 26, 2005 5:35 PM
OK, for what it's worth:
I had updated to 2005102603 (today, I think).
I downloaded and installed RC1 from the link above. This appeared to be version 2005102519. I installed it over the above version (2005102603).
I then did an update (from the "update" channel, no other updates were available through Update Channel Selector) and was back (ahead?) at 2005102603.
It would appear that the above version for RC1 was updated.
My question: Is this what the developers are expecting, that the most current version (as of today) should be 2005102603 ?
Again, submitted for what it's worth. Thanks again for all the hard work.
Sincerely,
Lawrence
Ithaca, NY
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051026 Firefox/1.5 - Build ID: 2005102603
Posted by: Lawrence | October 26, 2005 6:07 PM
Bug 307678 looks pretty nasty. I have a feeling it'll have high visibility. It should be a blocker, IMO.
Posted by: Remy | October 26, 2005 7:04 PM
The update system seesm to have been fixed. :]
Posted by: Jonathan | October 26, 2005 7:24 PM
Definitely not a blocker, but this is quite a GUI annoyance:
In the Print Setup dialog (File->Page Setup) under the "Format & Options" tab, switching from Portrait to Landscape (and vice versa) makes the bottom tab area jump wildly.
Posted by: Dave W | October 27, 2005 4:16 AM
I am going to nominate https://bugzilla.mozilla.org/show_bug.cgi?id=265736 as a blocker for FF 1.5, I just tested and it still crashes the test release posted above. It's marked critical but no one has gotten around to fixing it.
Posted by: Matt LaPlante | October 27, 2005 9:21 AM
@Asa, why don't u care for THUNDERBIRD RC in your blog? Why don't u link to these RC builds? It's like a wallflower here. -Amsterdammer
Posted by: Amsterdammer | October 27, 2005 10:02 AM
I'm having the bug too where force links that open new windows to open in new tabs is checked, sometimes works, but on most sites still ignores it and opens it in new window. Other then that no problems.
Posted by: Mike | October 27, 2005 12:16 PM
Mike, that's intentional (see bug 313300). I'd be interested to see a list of sites where it doesn't work the way you expect.
Posted by: Jesse Ruderman | October 27, 2005 1:45 PM
Mike, btw, you can change that back to the previous behavior by going to about:config and changing browser.link.open_newwindow.restriction from 2 to 0.
Posted by: Jesse Ruderman | October 27, 2005 1:46 PM
Yea I played with it some more and see how the behavior has changed. It used to open everything in the new tab of instead of new window, now it ignores new windows that specify a window size. So its working fine.
Posted by: Mike | October 27, 2005 2:49 PM
https://bugzilla.mozilla.org/show_bug.cgi?id=265736
ouch! that's diffenetly a blocker.
Posted by: yakster | October 27, 2005 6:54 PM
Agh! This for me should be a huge blocker:
It's installation delete's all your preiouss custom search engines!
It really sucks, I cant recover them... I had many of them that were custom made by me for my own personal needs... lots of hours of work. Lost!
Posted by: MTO | October 27, 2005 8:48 PM
Reported here:
https://bugzilla.mozilla.org/show_bug.cgi?id=314137
This to me is a blocker, it's as critical as deleting personal bookmarks.
Posted by: MTO | October 27, 2005 9:09 PM
Look here!!! http://www.positioniseverything.net/articles/onetruelayout/examples This is nasty CSS regression bug.
Regression from Firefox 1.x or RC1 - I don't remember...
It will be headache for web designers if you release good browser with this bug. :(
P.S. Also don't forget look here: http://www.positioniseverything.net/articles/onetruelayout/appendix/exampleresults (look at Firefox 1.5b1 row).
Posted by: FataL | October 28, 2005 8:38 AM
Any suggestion on how to test this for auto update?
Posted by: wayne | October 28, 2005 11:36 AM
https://bugzilla.mozilla.org/show_bug.cgi?id=314274 has been filed to address the CSS regression issue cited by MTO
Posted by: marcia | October 28, 2005 5:53 PM
Ever heard of "backing-up" your files......hehe
Posted by: Stefko | October 28, 2005 6:40 PM
Backing up Firefox profile... once in a while, yes, I do it.
Backing up program folder... no. I guess that is one of the (good) reasons why searchplugins are being changed from location... problem is all those who like me had custom searchplugins are going to see them dissapear without any notice once they upgrade.
Posted by: MTO | October 30, 2005 9:47 AM
Thanks for the update, Asa. I'm using the RC1 build on Windows XP SP1, and have found no problems/issues so far.
I did however read about a bug with CSS layout (floats and negatives), which has been submitted as "Bugzilla Bug 312777 Negative margins cause floated elements to be placed to the right of incorrect earlier boxes". I haven't validated this problem myself, as I'm not that much of a CSS expert.
More information at http://www.fu2k.org/alex/css/bugs/gecko1.8b2+_negativefloats/. Anyway, thanks for continuing to contribute to a quality product. Happy Halloween!
Posted by: Scott Wilson | October 31, 2005 5:56 AM
"Is it just me, or is the URLbar still broken? Right now I have 5 tabs. If I ctrl-pgup/pgdn through them, all but one show this blog post's URL as the URL of the tab. Basically, right now, the first three tabs' URLbars are broken. They show the URL of whatever newer (tabs 4 theough x) tab was up there before. Tab 6 now has Google.com, so the first three show that if I switch to them, etc. Basically, there just seems to eb massive URLbar breakage. Makes copying URLs hard."
Like Grey Hodge reported on October 26, 2005, I am also facing this problem. But the only extension I have installed is Greasemonkey.
Posted by: Vivek Jishtu | October 31, 2005 8:35 AM
I have to say the biggest bug that I still get is upgrading from 1.0.x -> 1.5 results in firefox no longer launching (on windows).
Standard 1.0 install, vanilla upgrade from a downloaded windows .exe isntaller, and afterwards when you run the new firefox it just silently fails. No errors, nothing, it just stops working.
This occurs with both firefox and thunderbird.
I can't see how we are close to an RC when you can even upgrade from a previous release properly :/
Posted by: koan | November 1, 2005 8:08 AM