New
#11
g1lly any sign of process isolation or sandbox in 6.0 builds? I would like to think they at least working on those considering IE has had both for a while now and chrome has them as well.
to be fair in my view the extensions is what makes FF what it is, without tabmix plus and ...... I wouldnt be giving FF a 2nd thought. All the extensions I use on FF3 seem fine on 4 tho. So I didnt have the same problem with compatibility, the one that gave me weird behaviour with mouse and fish test was a FF4 specific extension.
Last edited by Airbot; 15 May 2011 at 00:13. Reason: rule #20
They have IPC / Sandboxing on their roadmap but I don't think it's been implemented yet in the these early 6.0 builds.
https://wiki.mozilla.org/Firefox/Roa...Customizations
thanks for the info.
I have been reading what in my view is scary stuff about the future of firefox. Mozilla must be really shaken by chrome because they changing their dev policy to copy chrome as well. Things I have read included every 6 weeks will be a major release update and will scrap security updates instead merging them with feature updates. So if I want security updates but not feature updates I will be screwed.
Actually Nightly builds are 6.01a2 and more stable. They also address several pressing issues.
Now regarding downgrading to 3.6.17, very soon Moz is going to start pushing 4.0 downstream so it is a waste of time (in my opinion) since shortly you will be urged to update back to 4.0
There are ways to make all extensions work, it is 25% faster, and more stable.
I just installed FF 5 Beta 1, looks good so far, but it would be nice if extensions and plugins would be functional :)
Sort of what I was thinking. That's like blaming Microsoft for your 10 year old printer (or any other piece of hardware) not working with Windows 7 because the manufacturer didn't put out any drivers for it.
As Echo said don't blame Mozilla/Firefox, get on the extension writers case. That or look for extensions that are similar and that are getting updated. Can't blame Mozilla for your favorite extension not getting updated for who knows how long.
You can also do this,
Extensions.checkCompatibility - MozillaZine Knowledge Base
and then test those that are supposed to be incompatible. Probably find that most if not all will work just fine. Or you can go through all of your "incompatible" extensions and change the maxVersion number in all the install.rdf files,
https://developer.mozilla.org/en/Ext...ate_RDF_Format
which is all that most of the extension writers do anyway if there are no problems with their extensions in a new version of Firefox.