As of this morning, we're down to less than 20 bugs still blocking the 1.5 release candidate. Of those 20, there are only about 5 that still need patches so I think we're right on track to hit our lockdown on Sunday night.
Posted by: Kommet | October 19, 2005 9:32 AM
Posted by: Thomas Stache | October 19, 2005 9:46 AM
I guess they are skipping fixing the serious security bug in 1.0.7 and just releasing 1.5 ?
Posted by: koan | October 19, 2005 9:50 AM
Koan, I'm guessing that you don't know what a serious security bug is. If you're referring to the bug reported on slashdot, it has zero security implications. Every browser has known crash bugs. There isn't anything interesting to me about a rare crash bug that cannot be used to trigger a buffer overrun or similar security concerns and this bug doesn't trigger anything like that.
- A
Posted by: Asa Dotzler | October 19, 2005 9:53 AM
Awesome news, Asa! It was a very pleasant surprise when I checked to see if my nightly build had an update and I saw the update was labeled version 1.5. I can't wait to help spread the news that 1.5 is available to everyone.
Posted by: HardinComp | October 19, 2005 10:06 AM
Firefox has officially reached 1,000,000,000+ mark! I'm sure you already know but post your thoughts/thanks we'd like to hear them.
Posted by: Yakster | October 19, 2005 10:36 AM
Sorry to get your hopes up I mean 100,000,000+
Posted by: Yakster | October 19, 2005 10:38 AM
koan: Please see Secunia's entry for Firefox. They rate security flaws on a five level scale: the worst are Extremely critical, then Highly, Moderately, Less and the lowest are Not critical. Secunia describes the DoS flaw that was mentioned on Slashdot as "Not critical". The worst open flaw in Firefox is currently "Less critical". Contrast that with Internet Explorer... Their worst open flaw is "Highly critical" and is over two years old!
Posted by: Limulus | October 19, 2005 10:39 AM
HardinComp: 1.5 has NOT been released. Version string on nightlies updating to 1.5 is not the same as 1.5 official being released.
Sigh.
Posted by: Nitin | October 19, 2005 11:05 AM
simple question,
Since there are only that few bugs still blocking the release, is one of them the bug that breaks new windows from being openen? i had that problem ever since i upgraded to beta 1 on my linux machine, and my coleage had the same problem om windows.
Since i did comment on the bug in bugzilla, but it didn't seem to get noticed i figured i'd post it here.
It would be a shame if some obscure bug disallowed a given percentage of users to open links with _blank as their target, or javascript popups.
Posted by: jan | October 19, 2005 11:26 AM
Erm, I don't know about you, but I don't want pages popping up in new windows.
Posted by: thepineapplehead | October 19, 2005 11:52 AM
I'm sure Neil will be happy with this link :D Thunderbird auto-update hasn't worked for me.
It's good to see Firefox at full speed again, it's been almost a year since 1.0 :D
Posted by: Joe Anderson | October 19, 2005 1:16 PM
jan i had that problem... i ended up uninstalling FF completly (installing over the top didnt work) and installing again
Posted by: Dominic | October 19, 2005 4:26 PM
Yes but Firefox continue to have bugs https://bugzilla.mozilla.org/show_bug.cgi?id=33654 5+ years older. I think it's not acceptable.
Posted by: Malix | October 20, 2005 5:54 AM
thepineapplehead -> its the user initiated clicks that break down, not script based popups, they get and should be blocked.
I actually get an unhandled exception in my javascript error log, stating that window.open failed without any reason. (something breaks firefox's ability to open new windows, and makes the window.open function break.)
Posted by: Jan | October 20, 2005 6:08 AM
Is the 1.5 Beta 1 to 1.5 Beta 2 autoupgrade rollout being skipped?