Forum Moderators: open
Catch up on what was new in beta 1 and beta 2:
[mozilla.org...]
[mozilla.org...]
and live tomorrow:
[mozilla.org...]
Technically what's new:
[squarefree.com...]
and previously:
[squarefree.com...]
[squarefree.com...]
[squarefree.com...]
[squarefree.com...]
and really technical "what's new" for developers [simon.incutio.com]
Behind the scenes: 40 bugs still listed for 1.5 [bugzilla.mozilla.org]
You are going to make sure all your extensions are up to date for this release, it's critical.
TIP: easiest way to look at all your extensions & themes to track them for updating:
[mozilla.doslash.org...]
Basically I go down the list of hyperlinks the above makes and just check for current versions and/or complete changes for 1.5 support.
If you are a developer/programmer using javascript & css you might want to look at the nifty Console2 extension for 1.5 [forums.mozillazine.org]
That feature will be all the rage for websites/forums to tell users about
since it is not activated by default and the newbies will think the posters are gods.
By the way if you are not using FasterFox, you should be:
[fasterfox.mozdev.org...]
Makes all the little speedup tweaks you think you should be using easy to access.
last but not least:
Code lockdown for 1.5 Release Candidate 2 will be this coming Friday November 4 at 11:59pm PDT.1.5 Release Candidate 2 may be released as early as November 11 depending on the feedback from RC1.
Fastback is on by default these days -- that linked article is out of date.
Another useful feature is "Clear Private Data", which lets you wipe out "sensitive" stuff (cache, history etc) on demand or when the browser is closed.
Extension and theme management is improved behind the scenes, although as always there'll be lots of breakage until everything's updated. I hardly need note that many of the best features of Firefox are provided by extensions rather than the core install. Scrapbook, Adblock (and the Filterset.G updater) and Download Statusbar are just a few that make the experience so much more worthwhile.
The new binary update system should be working, so in future there won't be any need to download 5MB of data just to patch a security hole.
There's also a new options dialog (isn't there always?), quite a number of security fixes, and some initial support for SVG.
The biggest step back in this release is the odd appearance of the menus when used with Windows Classic. There is an extension to correct this problem, which will be going away with native menu rendering in the next major version. That patch was too buggy to be accepted in 1.5.
It's up to extension authors to make sure they are compatible with new releases, and RC1 has only been out for 12 hours :)
Yep, that's exactly why the version I use is always an older one (using 1.0.4 right now). I find it aggravating to suddenly have the features that I like most about my browser suddenly disappear on a supposed "update". (I never did get "Calendar" back when I went to 1.0 - I believe that was the update that killed it - not sure).
Why exactly should I use the latest version of Firefox if the more important extensions aren't part of it? If there is no version 1.5 for Flashblock, Littlefox, Google Pagerank Status, Reloadevery, etc, the browser is not ready, other than for beta-testing. For my own daily use, I'd rather be back to 1.0. The bloody thing has been constantly crashing ever since I went to 1.0.4.
Why exactly should I use the latest version of Firefox if the more important extensions aren't part of it? If there is no version 1.5 for Flashblock, Littlefox, Google Pagerank Status, Reloadevery, etc, the browser is not ready, other than for beta-testing. For my own daily use, I'd rather be back to 1.0. The bloody thing has been constantly crashing ever since I went to 1.0.4.
Start a new profile with 1.0.7 and then add in your extensions and you'll be fine. The fact that you are having problems is probably due to profile corruption a while back.
And OF COURSE not all the extensions and themes work with 1.5 yet. 1.5 hasn't been released yet. This is the first of at least 2 release candidates after the 2 betas that give developers time to update their extensions and themes and everyone time to bang on it and see what breaks.
the extensions are extremely usefull but it's getting to the point where you need to split the extensions across two or more separate simultaneous installs of FF to avoid either one of them crashing ..unless you are running 1 gig or more of RAM ..
and if you take out the extensions ..you are left with what amounts to a much slower opera ..
I keep it ,I like it.. but I use it less and less and certainly not the "latests" till they are at least 30 days old ..and ironed out ..
I hear you that this release is primarily for developers. I gotta say though - if the thing is breaking many extensions whenever they change it, they have to rethink the approach. I'm a loyal Firefox user, but it certainly taxes my patience - the extensions are the biggest part of it, and if they're not all along for the ride for every update, there shouldn't be an update. I confess that I'm totally ignorant on the code (and not really in a position to criticize), but I have to ask - why aren't the updates backwards-compatible with the extensions and themes?
I like fire fox immensely but I have already too many instances of "there is a script on this page which is slowing down firefox would you like to abort " happening even here on WebmasterWorld if one switches to code view
This is interesting. I've only run into that "script slowing down Firefox" error about three times since version 0.6. I'd like to see if I can duplicate your problem myself; unfortunately, I don't know what you mean by switching to "code view." I didn't think WW ran any clientside scripts at all, so obviously I'm missing something somewhere along the line.
1.5 represents a major update to Firefox and the model for extensions actually changes a bit. I believe the reason that they don't automatically let the older extensions work with the new FF is because they may do Bad Things (tm). Either that or they just may not work at all. So, the extension developer has to try their extension out on the new FF 1.5 and then alter it once he's confirmed it works to say that it works.
Pre-1.0, the extension API changed quite a bit with each release, so it was necessary to try your extension out on each successive version. But, that's to be expected with beta software as well. Once 1.5 is out, all extensions should be updated pretty soon afterward and then the extensions api should remain unchanged (barring any bugs or security lockdowns) until FF 2.0.
I like fire fox immensely but I have already too many instances of "there is a script on this page which is slowing down firefox would you like to abort " happening even here on WebmasterWorld if one switches to code view ..it is becoming to much of a RAM HOG ..
I've found FF 1.0.7 very stable and have never encountered the error you're writing about. I've got 10 extensions running on it. There are a handful of problematic extensions, though.
I like fire fox immensely but I have already too many instances of "there is a script on this page which is slowing down firefox would you like to abort " happening even here on WebmasterWorld if one switches to code view ..it is becoming to much of a RAM HOG
1.5 fixes both of these issues.
"script abort" timeout setting is here:
[kb.mozillazine.org...]
dom.max_script_run_time
serch for it in about:config - the default is like 5, change it to 10 or 15
also make sure browser.cache.memory.capacity is set to 32767, no higher
The upcoming Lightning project integrates said calendar directly into Thunderbird and is something to watch. You can actually mess with it a bit now, if you want, as they are doing nightly releases of Thunderbird builds and matching Lightning XPIs.
Here's the link to Thunderbird/Lightning nightlies (not for the faint of heart):
[ftp.mozilla.org...]
In a word WOW. I think this is the first version that is visibly faster than IE6. It even starts visibly faster. Nice work!
If anyone is curious here are the extensions I swear by (list made by InfoLister)
Extensions (enabled: 22, disabled: 0; total: 22)
Plugins
I've reinstalled 1.5 and managed to get new versions of most of my favourite extensions by going to their homepages (it was using the "update" from tools/extensions that was messing things up - they should put a warning in that to not even bother trying).
It works quite well - definitely faster. No crashes yet, but it will take a few days of surfing to know if it's more stable than 1.0.4.
There is no Calendar extension for 1.5 yet that I could find, but I dl-ed Sunbird.
Many thanks for the posts in this thread that supplied suggestions and help.
I just renamed the \firefox folder to \firefox10 and the profile folder to .old and it's as good as invisible to the new Firefox install.
Yep, I should have thought of that.
Still no crashes. I've been testing it with sites that were causing problems before, and no problems. It's terrifically stable and quite agile. Mind you, I was happy with Firebird too - the thing is moving along nicely though, eh?
I've been taking the nightly rc2 releases and it fixed one plugin problem I was having:
[ftp.mozilla.org...]
Looking good! I'm all ready for 1.5 final... should be big news...