Slashdot Mirror
Mozilla Firefox 1.5 RC3 Released
Jasper Bryant-Greene writes "It doesn't look like the official website has updated yet, but Firefox 1.5 RC3 has been just been released. MozillaZine has the scoop."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
I hope IE is updating their notes on what to incorporate in to IE7 *rolls eyes*
"hey, could you pass me a paper towel? er.. I mean... DEPLOY ABSORBTION PANEL!"
Any news about when will the Mozilla Foundation release the final version? Hopefully, it will be around the first two weeks of December 2005.
I was in the middle of typing a posting and this thing popped up taking away focus.
Didn't have full time to check, but hitting return would/could have started the update process off without informed consent.
I realise they want to get it updated, but I think the new regime is just a bit too forceful - it should be on application startup and not checking whilst I'm browsing.
liqbase
Not to be a troll or anything, but why does slashdot deam every minor release of Firefox to be worthy of a story? Its no different from any other OSS. And also, anyone who uses Firefox would notice and know what the little green upward-pointing arrow on the upper-right-hand corner means.
I love FireFox as much as the next guy but we need to stop bragging about "100 million downloads !!!" when a new version is out every few weeks.
My firefox prompted me a few hours ago about an "important upgrade", which I did. But it didn't say what this upgrade was about, and therefore I don't know if I'm running RC3 or not. It would be nice to know what has been downloaded.
Good work Mozilla. I can't wait to see the source to look if they cleaned it up yeat. Last time I built mozilla from scratch is was filled with switches which where not supported for ages (like native qt support).
And the truncating title text bug that arbitrarily drops information from websites still hasn't been fixed. It's now five years old! Hooray!
5
https://bugzilla.mozilla.org/show_bug.cgi?id=4537
I think Moz is a great project, but I use Opera because things like this are allowed to linger for um, half a decade, instead of being fixed.
dinosaur comics
http://developer.mozilla.org/devnews/index.php/200 5/11/17/15rc3-available/
Notice that RC will be the final version if there are no new bugs.
No. It may say "Firefox 1.5" in the About box, but it is one of RC2 or RC3 at this point. It doesn't say "RC" in the version string because then it would not, in fact, be a candidate for release; they would have to change the version string and rebuild.
Mozilla are doing thing The Right Way, which is rare these days. They even follow the proper definition of Alpha & Beta, which is even rarer.
I have been running rc2, and it works well but it does have some freezing issues.
0 5/11/17/15rc3-available/ (The release notes blog):
From http://developer.mozilla.org/devnews/index.php/20
* A recent regression that either crashes or breaks certain usages of innerHTML for dynamic applications. (315189/315999)
* A recent regression and most common RC2 crash (316025)
Hopefully, this will resolve most of my issues.
Remember, if you can't wait a day or so for the auto update: Help -> Check for Updates. (If you are running a RC of 1.5)
Kudos for the dev team.
They fixed the drag-and-drop crashes I was seeing all the time in RC1/2. It was getting really annoying having the browser lockup all the time whenever I accidentally dragged a tab or some text.
So, this happens on sites all over the net. News is disseminated instantly over a large number of sites instantaneously. What makes slashdot good are the users who make good comments. You want a better site, quit whining and do that. The commentary is why I come here and digg's is not that good. Tech news I can get almost anywhere.
As for politics, more and more it is impacting the nerds of world due to nervous politicians and evil content companies pressuring them. We would be remiss to ignore it.
This thread is for FF RC3. I got mine automatically yesterday with no hitches. Considering how the last time I got an upgrade message it flopped about four times, this was an improvement.
has been just been released
I hear the new RC has a grammar and spell check that automatically fixes slashdot before it loads...
"Some days you just can't get rid of a bomb."
Every time I use firefox and open a few tabs my vm size goes to 1GB. It's getting ridiculous how developers of firefox are ignoring to fix this problem. I hope they fixed this otherwise it gets uninstalled once IE 7 comes out Apart from tabbed browsing and few cool addons It's just not worth it in my opinion.
sweet
To quote Asa Dotzler,
There are 11 types of people in the world: those who can count in binary, and those who can't.
That drives me even more insane than usual. There is absolutely nothing like cancelling a long download or initiating a time-consuming update, or hell, REBOOTING THE FUCKING SYSTEM, because of that.
* Actually, I think TweakUI might do just that. I may even have it installed with that option set on my Windows box. It's just a bit too long in the tooth to play the latest games, so I haven't used it lately.
Sticking feathers up your butt does not make you a chicken - Tyler Durden
It is serious. I have the same issues, up to 1.5 rc2 and the 1.0.x series.
I just upgraded tp rc3 but its too early to tell if that was fixed.
The parent should be modded up - this is a LONGSTANDING issue that has not gotten any attention.
I have 1GB of RAM (FF usually peaks at about 160MB for me before I restart it) so I dont care that much, but I know lots of users on lo-mem systems who are highly annoyed by this behavior and switched to Opera. I think this kind of thing should be a high priority critical/major bug and receive attention ASAP.
Lord High Crapflooder The Right Honourable Vlad Craig Esther McDavenpherson III
Destroyer of Mercatur.Net
How great of both TFA and the Firefox 1.5 "What's New" page to not mention the Unofficial Firefox 1.5 RC3 changelog from The Burning Edge.
'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
(Slightly veering away from the topic) Mobile phones also annoy me in this regard. If I'm typing a message, browing a menu, or doing something else on my phone and someone calls, the phone switches straight into answering mode, in which the button I was just about to press has a completely different function. It's then a matter of complete chance whether I answer or reject the call, or send it to voice mail.
This problem could easily be solved: when the phone changes modes due to an event not initiated by the user, disable the buttons for a couple of seconds to allow the user to react to the change of state. Do any phones do this? I've not seen one that does.
If your comment title says 'Re: Foo', I'm not likely to read it.
MS uses ActiveX scripting objects to support additional languages, so doing it the MS way would require blanket support for ActiveX. That actually wouldn't be difficult to do in FF for Windows, but it leaves FF out in the cold on every other platform. It also sets a really bad precedent.
This could also be supported through the plugin architecture, but that puts us back in the 90's, where sites commonly required proprietary binary plugins or ActiveX controls. We already know that's a developmental dead end and a security nightmare. The current JavaScript architecture however, is an open ECMA spec that is directly addressed in the W3C standards. The presense of and adherence to these standards is one one the major factors contributing to the current explosion of new web technologies. I agree that AJAX is a silly buzzword, but at least it's keeping browser and web developers focused on standards support and interoperability.
I do think there is still a vacuum for a language Nuetral VM with a strong security sandbox that can hook into the DOM. Java applets should have filled this niche, but Sun repeatedly botched the delivery. MS .NET client web controls are another option, and Mono can provide support on non-MS platforms. Unfortunately these don't really seem to be going anywhere. I'd really like to see something in this arena catch on, but interoperability and security are essential for that to happen. And blind scripting interfaces won't provide that.
Now, language independence for extensions and internal development is a different issue. If you had done a little research you would see that Mozilla has had Python support for years, but it's not in the release versions. A little more research would probably land you at the Gecko roadmap where you'd find some info on the language neutral DOM interface in Gecko 1.9. Poking a little further would probably lead you to XULRunner. At that point I hope you will see that the intent of the development is quite intelligent and open. The fact is that it just takes time to get there and there are lot of factors to consider.
P.S. - I'd also suggest taking a closer look at JavaScript before calling it a brain-dead language. It's far from perfect, but certainly more intelligible and maintainable than Perl when used properly. And for it's target environment it actually works quite well.
Yes, yes I do come here for the commentary. Most of the time it is very good if you set your preferences right. Do you get goofballs, sure, show me a site where you don't. Frankly, it's people like you who lower the bar. Another whiner who instead of taking his/her show on the road to a site more suitable to you sits here and cries.
Don't like us, hang on here and I'll get you a lollipop.
It is subjective to be sure, and it has to do with reading comments from people who think, not just react (often with idiocy). Along those lines my subjectivity excludes comments like yours from the "good" pile.
Mind, this often comes from AC category. Most of whom have good reason for not identifying themselves.
You want Fasterfox for this:
Block Popups:
A popup blocker for popups initiated by Flash plug-ins is also included.
Fasterfox
fak3r.com
If they are wondering what Firefox will be implementing, they might as well look here ;-)
Clever signature text goes here.
To say the Mozilla people "have been refusing to investigate this bug for 2 1/2 years now" is a gross mischaracterization. It was right for them to mark this bug as invalid because it's not a bug. What it is is a collection of symptoms running the gamut from crashes to extreme memory usage to cpu hogging.
The folks at mozilla are fixing these sorts of bugs all the time. But since the report is too vague to let the Mozilla coders know when the bug that caused the crash is actually fixed, it could never be marked fixed.
In short, it's "not being investigated" because it's vague, unreproducable, and simply duplicates a large number of more specific bugs.
You want the truthiness? You can't handle the truthiness!
I don't think this is completely unacceptable. You have to install it as root/admin to begin with, so just imagine that running Firefox one time as root/admin is simply the last step in the installation process.
Having said that, I can't imagine it being too hard for the installer to initialize the installation without manually having to run Firefox. Why don't they?
Second the HTML specs do not say exactly how things should be rendered. This bug is open because it is some people are saying "I think the spec should work like this" where the spec does not absolute.
There isn't any serious disagreement over what the HTML spec says here. The reason it hasn't been fixed yet is that fixing it requires fixing bug 228673, which is in a fragile part of Mozilla's code (XUL layout) whose original authors have probably left the project. I see a patch and "[reflow-refactor]" in 228673, so it (and the tooltip problem it causes) will probably be fixed early in the Gecko 1.9 cycle for Firefox 3.0.
The shareholder is always right.