Slashdot Mirror
Mozilla.org Releases Mozilla 1.0 Release Candidate
asa writes: "Today mozilla.org made available for download binaries of Mozilla 1.0 Release Candidate 1. RC1 will be used to gather feedback and crash data in preparation for an RC2 or a final release. Please hammer on these builds, report bugs and send in talkback reports.
New to RC1 are fixes for about 2000 bugs including more than 150 crash fixes so grab a build and let us know what you think."
Got it and have no compelling reason to switch back to IE except for Windows Updates. (Under Linux at home I am still going to use Galeon)
Nic Farley
This release seems like a very stable release. I've been running it for many hours now (compiled from cvs) and it has been faster and generally more pleasant than MZ0.9.9. And I really like the new download manager =). Mail return recipts aren't bad either!
Anyway, Moz 0.9.9 had a bug where we could only see positively charged particles. But the good folks at mozilla.org fixed that right up for us. Now if only they'd patch it so we could see particles with no mass...
Some time ago I read an article on newsforge that it's really easy to switch from IE to Mozilla when using it as a html viewing engine -> the calls are all exactly same.
Now I'm thinking.. Is it possible to switch that in already build (binary) application? Like ditch that mshtml.dll or something like that?
fucktard is a tenderhearted description
I'm using Mozilla 0.9.9, and even that earlier version is excellent.
Good work, Mozilla team.
I know that some people will have trouble with a warm statement such as this, but here it is anyway:
Mozilla is an act of love. There are many ways to be loving, and supplying a much-needed tool to the whole world is one of them.
-- The Mozilla Team
Yeah, the biggest reason everyone where I work is getting exited is because the View Source bug was finally fixed a week or so ago, and this is the first major release that will incorporate the code.
Woohoo!!
the announcement that rc1 is near goes on the front page and the day it's released it slips into the developers section
/.
I got the 10meg Windows version in 5 minutes and that's across the atlantic (caches not withstanding)
thanks
I guess the FreeBSD port will be updated over the weekend, my cron will auto upgrade that one in the wee hours.
I hope my favourite bug of not displaying the url in the address bar until you press refesh has gone
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
I'm running RC1 with crash feedback and boy, someone gave it a turbo boost!
;)
well done thank you thank you thank you er AOL
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
The prophecy is coming to pass! Repent sinner, the end is nigh!
Optimoz: add gestures to Mozilla.
Enigmail: add PGP/GPG support in Mozilla Mail.
Googlebar: the cool Googlebar for Mozilla too.
And if you want more just look in MozDev and you'll find something interesting.
Andrea
I thought it was Christmas in April:
From What's New In This Release
The preferences dialog now allows you to set a minimum font size for web content.
I suppose this feature prevents web sites from forcing my browser to display tiny, tiny font sizes on my 1600 x 1200 resolution monitor. If this is the meaning, however, I could not get the feature to work. (See Edit/Preferences/Appearance/Fonts/Minimum Font Size.)
If that is the meaning of that feature, then it will solve the most vexing problem I have with browsing. Most web sites over-ride my font size selection, and display fonts in sizes that cannot comfortably be read.
But, the feature doesn't work now, so maybe I will have to wait until May for Christmas. *grin*
(sorry)
There's still the (windows) bug in the classic theme, where when you minimize mozilla, it doesn't. Which sucks because I like classic.
Got friends?
Comment removed based on user account deletion
You can find out about it here: http://www.iol.ie/~locka/mozilla/mozilla.htm. One of the biggest drawbacks is that there is no scripting.
Quick plea - if you have filed an unconditional bug that hasn't seen activity for a month or two check whether it is still valid. If not resolve it worksforme. Thanks.
With all this increased testing, more and more bugs are being filed at increasingly speedier rate and the Bugzilla database could always do with an extra hand to stop bug counts spiralling out of control.
Plug
Over in #kill-unco on irc.mozilla.org we are trying and reduce the number of unconfirmed bugs. The more help we get, the sooner people's complaints are serviced and the sooner they can be fixed.
Sometimes unconditionals slip through intial net of bugzilla marshalls and just wind up being forgotten about. This can happen because the intial marshalls don't have access to the same platform or don't use a particular component much (macs, mail and news/java spring to mind). Other times the reporter doesn't file enough information and needs to be prompted for more. Often unconditionals are filed subsequently fixed by other bugs but not closed by their original reporters. All these things make for a messy database and engineers could use up
time marking dups rather than fixing bugs.
A few moments of your time could save engineers from going mad seeing the same bug reported by reported in 30 different places. If each slashdot reader helped resolve just two mozilla bugs a day then we could all get a better browser...
RC1 has bookmark groups - this means that with one bookmark you can open a large amount of pages that'll start loading in various tabs.
0 0 - copy/paste yourself, no linking from slashdot allowed), we will almost certainly see a release candidate 2 before the final version of 1.0 will see the light. (Though I could imagine RC1 performing so well that they'll integrate RC2 with 1.0 final after all.)
Also, as evidenced by bug 138000 (http://bugzilla.mozilla.org/show_bug.cgi?id=1380
*kicks self* Must not post while tired - bookmark groups _are_ mentioned in the release notes.
Posted with:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020418
Downloaded the i386 RH 7.x RPMs and rebuilt on RH 6.2. Works like a charm.
Thanks, Moz team!
Using your sig line to advertise for friends is lame.
I'm hoping they fix 130614 soon. I've got a Win98SE box which I cleaned up using Revenge of Mozilla (thus making it much like win95), and this is keeping me from using recent versions of Mozilla on that box. Fortunately I don't use that box very often.
-- $SIGNATURE
Why the heck isnt this on the frontpage? Mozilla *needs* testers especially right now and were stuck in the developer section??
Especially since the articles saying Mozilla 1.0RC will be out soon was posted on the frontpage. Come on slashdot lets go!
Moz sure has shaped up since the early betas!
I hope after 1.0 is realeased the developers will have time to finally address the completely unstable plugin interface on Linux (plugin barfs ==> Mozilla crashes).
[not complaining, just anxious to have resolved what is IMHO a huge bug]
Thanks for reminding me. But, I couldn't get that to work either. So, maybe I need to reboot. Maybe the OS is confused (Windows XP). Windows XP is better than other versions of Windows, but still flaky.
"mozilla.org PLANS to release 1.0rc1 some time in the future" is front page news, but "mozilla.org releases 1.0rc1" is fucking backpage non-front-page Developer news?! What the hell?!
I've been using the nightlies since 0.9.9 and they've all been good and getting better.
-- @rjamestaylor on Ello
Perhaps one of the developers will chime in and help clear this up. I believe Talkback builds are put together to catch crashes and return valuable data back to the development team. A similar question could be asked of coredumps on Unix boxes—they help because they allow post-mortem analysis.
Digital Citizen
The non-MacOS X version is now described as being for MacOS 9.x. I tried to run it on my 8.6 system and it hangs on launch. 0.9.9 was described as being for 8.x and 9.x, and it runs fine on 8.6 (I'm posting from it). I know, maybe I should upgrade my OS, but my company won't spring for any Mac upgrades, and I run a slower PowerMac at home - MacOS 9 is too slow for it. Rats. I've been looking forward to final on Mozilla and now I can't run it.
No sig? Sigh...
Have they even bothered to testing this version?
I don't think so, the preference is broken, categories cannot be selected, so it's not possible to configure Mozilla. I cannot configure my proxy, so my testing has not gotten very far.
So I pop over to the BugZilla site to report the bug, and I have to start jumping through hoops, why the need to pre-register to report bugs? What happened to the idea that many eyes make bugs shallow ?
My advice wait for the next release candidate.
Normally I like to experiment, but I just upgraded from 0.9.9 (with mozdev spellchecker working OK) to RC1, and somehow its still picking up the spellchecker (how, anyone?!) and locks up the machine EVERY time I try to send email!!
So I've rolled back to 0.9.9 again, and although it recognizes the spellcheker, I still can't send email.
F**k that!
To be honest, leave the alpha add-on's until 1.0 and frozen API's - because in the meantime how are you supposed to know what is RC1's fault, or something to do with whatever random XPI you are running.
If you want to help log bugs for projects - great!
But right now we need to know what's wrong with the Moz RCs, and there's no easy way to tell that if you have X alpha extensions plugged in!
Until there is a stable 1.0 of Moz with frozen APIs then debugging these alpha projects is a hopeless task, which I should think is why most of the projects at MozDev are stale at best!
The best way to help MozDev projects is to ensure that Moz 1.0 is as bug free as possible - they they can have something stable to build against!
Don't install over an exisiting Moz directory, clear it out, then do the install.
I've had the same issue on the RC1 nightlies on Windoze, there is a mention of it somewhere on the release notes... somewhere...
But this release is really quite nice, I'd hate to see it not get used for something thats really pretty minor.
As one of the other comments suggested deleting your profile/mozilla directory an reinstalling may fix this. Take a look at http://bugzilla.mozilla.org/show_bug.cgi?id=137952 for further detail.
There are those who believe that with a little help from everyone, Mozilla will become the best browser on every platform. And there are those who believe that Mozilla "sucks" currently, or laziness sets in, so there's no reason to help out at all. For the first set, I invite you to check out http://www.mozilla.org/get-involved.html. With just a bit of your time, you can help make Mozilla the best browser on any platform. And every time you spend 15-30 minutes helping out the project in whatever way you choose to, keep in mind that someone else has spent 30 minutes helping fix something that won't be a problem for you. That's why it works.
In the end, if something you come across isn't working, and you do nothing to help, then it's your fault. The project only gets better when you do the work to properly post your bugs to Bugzilla.
- Adam
If you had RTF Release Notes, you would have removed your previous install of Mozilla, and wouldn't have these problems. The only bug here is the "shouldn't have to uninstall Mozilla for every update" bug.
Of course bug reports require preregistration: 1. it limits spamming of the bug db, 2. it enables differential permissions, 3. it makes sure that bug reporters are kept up to date on progress.
WTF was this moderated as funny? It is freakin TRUE!