Firefox 5
-
After upgrading I had several kinds of trouble. So I reverted back to 4.x (the previous Cannot recommend 5 at this point in time. :mad: :mad:
I've got an issue with FF5 not loading custom fonts in locally stored webpages. German Vista Ultimate 64bit...
-
After upgrading I had several kinds of trouble. So I reverted back to 4.x (the previous Cannot recommend 5 at this point in time. :mad: :mad:
-
I also noticed nothing new but had no problems. You should still upgrade. I also looked up what has changed: Added support for CSS animations The Do-Not-Track header preference has been moved to increase discoverability Tuned HTTP idle connection logic for increased performance Improved canvas, JavaScript, memory, and networking performance Improved standards support for HTML5, XHR, MathML, SMIL, and canvas Improved spell checking for some locales Improved desktop environment integration for Linux users WebGL content can no longer load cross-domain textures Background tabs have setTimeout and setInterval clamped to 1000ms to improve performance Fixed several stability issues Fixed several security issues http://www.mozilla.com/en-US/firefox/5.0/releasenotes/[^]
-
I had one issue after I upgraded to FF5 from FF4 on my Mac: Slingbox client balked until I restarted FF in 32-bit mode. I went through this on Safari when it went 64-bit in Snow Leopard, so I'm used to the issue. Never run Chrome, can't say what happens there.
-
The upgrade broke the Pentadactyl extension. Updating to Pentadactyl's nightly build made most things work, but a few things are still broken. E.g., on Facebook the text fields do not scroll properly and you have to escape the Enter key with ^V. Another user reported the same symptoms on IRCCloud.
-
Yes I upgraded. I like it. I am just a little :( About IE 9...This Browser war is making me "pull me hair out" wait I don't have any... :-D ... I personally am starting to tend to Google Chrome...But unfornately, developers must be flexible?LOL!
-
That's because you haven't got the latest version. Firefox 5.0 was out just 6 weeks after version 4.0 So it looks like you will have to upgrade it every 6 weeks now or uninstall it. Firefox 3.5 would let you know if a page has any RSS feeds in the address bar. After upgrading it has lost this feature. Guess my idea of upgrading is not the same as Firefoxis! As they are up to version 5.0 and they now upgrade every week equals: 5 x 6 weeks = 30 weeks ago from the first version. :o)
-
Check this out: http://www.zdnet.com/blog/networking/firefox-5-new-but-improved/1196?pg=2&tag=mantle_skin;content
"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"
-
Up until yesterday, I hadn't noticed a difference between FF4 and FF5 (aka FF4.0.1) However, I have seen a stability problem which essentially not only locks up FF5 but also the whole computer when my 3-year old daughter tried to run some of her Nick Jr Flash games. Now many of the games were developed years ago (even prior to Flash 8) and unlike Google's sandbox of Flash (which catches the occasional crash from those games), Firefox 5 seems to do a worse job of handling the crashes.
James Wallis Martin JB Metrics Ltd, Director www.jbmetrics.com www.erpthree.com
-
I am currently using Firefox 7.0a nightly build, and browser is faaaast...
-
Memory footprint is much less than in 4.0 Also the plugins doesn't start to consume cpu like grazy yet :-)
-
I haven't noticed any problems.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Maybe, but its very odd. I can only get the local copy of this file[^] to load with its font by following a link from another page. If I try to load the page directly, by opening it in a new tab from the file system or by pasting its link into FF5's URL box, the font doesn't load. This only happens in the local mirror of my website. On the web everything seems okay. Strange... I've decided to develope my pages with another browser for the moment, and give the problem some time to go away. :)
-
Chris Losinger wrote:
now that i have it, i still don't know why it deserved a major revision.
They're trying to catch up with IE and Chrome.
The 3-legged stool of understanding is held up by history, languages, and mathematics. Equipped with these three you can learn anything you want to learn. But if you lack any one of them you are just another ignorant peasant with dung on your boots. R. A. H.
Glad someone started this topic. The whole versioning of a software is a very vague /to me at least/ concept. I'm sure there are numerous ways people can choose how to follow come up with their versioning standards. For example: according to time, like quarterly release of major version and what not, or major core change and complete rebuild /which is what most people are used to/. Unfortunately Chrome chose not to pay too much attention at the version of the product and just roll the software along. I'm sure they're going to come up with major changes in the core and whatnot but I doubt they're gonna mention it and use it as a marketing tool. Safari, uhhhh... yea IE, i believe is following the traditional microsoft way: release, get-feedback, rebuild on feedback and tech, release cycle, where each cycle is a major version, I'm ok with that. FF is an open source development, leaving it no choice to have major builds running separately making everyone to have a choice to upgrade. Then their versioning which just screws up with everyone's belief in every major version is a brand new different browser, where in fact they announced they're not going down that path. I think they're trying to lure people that use IE by saying "IE comes up with a new version every so often, so do we." This just reminds of a line in the "Tron: Legacy" nothing's changed it's just a new number. In the long run I think FF's gonna loose a lot of users if they don't: 1. quit asking about upgrading and just upgrade 2. quit making up new major versions, when nothing really is changed, at least as far as anyone can see. OR go as chrome, leave the whole versioning from the title. If(FF4 == FF5) return FF; my own conclusion: if you're going to have frequent upgrades, leave the versioning to the eyes of the developers and those who actually read changes.txt. Even though there are no written rules, but major versions should only be given to those softwares that have changed their core library AND redesigned the interface. I know people at mozilla will have answers and everything,
-
-
I did. Everything's fine except an add-on that seemed to be incompatible, but I can't remember what it was so after all it should have been something almost never used. About apparent no changes from FF4, it could be that they are trying to give the sense of innovation that (strangely) is given by the IE versions marketing. I don't bother if the interface looks the same, it is not the way I judge software major releases. I suppose there must be something changed in the core, and maybe that was already almost ready when FF4 shipped. In the worst case, there must be at least security enhancements. And since it took me almost no time and no efforts to upgrade, why not?
-
-
Glad someone started this topic. The whole versioning of a software is a very vague /to me at least/ concept. I'm sure there are numerous ways people can choose how to follow come up with their versioning standards. For example: according to time, like quarterly release of major version and what not, or major core change and complete rebuild /which is what most people are used to/. Unfortunately Chrome chose not to pay too much attention at the version of the product and just roll the software along. I'm sure they're going to come up with major changes in the core and whatnot but I doubt they're gonna mention it and use it as a marketing tool. Safari, uhhhh... yea IE, i believe is following the traditional microsoft way: release, get-feedback, rebuild on feedback and tech, release cycle, where each cycle is a major version, I'm ok with that. FF is an open source development, leaving it no choice to have major builds running separately making everyone to have a choice to upgrade. Then their versioning which just screws up with everyone's belief in every major version is a brand new different browser, where in fact they announced they're not going down that path. I think they're trying to lure people that use IE by saying "IE comes up with a new version every so often, so do we." This just reminds of a line in the "Tron: Legacy" nothing's changed it's just a new number. In the long run I think FF's gonna loose a lot of users if they don't: 1. quit asking about upgrading and just upgrade 2. quit making up new major versions, when nothing really is changed, at least as far as anyone can see. OR go as chrome, leave the whole versioning from the title. If(FF4 == FF5) return FF; my own conclusion: if you're going to have frequent upgrades, leave the versioning to the eyes of the developers and those who actually read changes.txt. Even though there are no written rules, but major versions should only be given to those softwares that have changed their core library AND redesigned the interface. I know people at mozilla will have answers and everything,
fuximus wrote:
In the long run I think FF's gonna loose a lot of users if they don't:
1. quit asking about upgrading and just upgradeOn the contrary: when software starts to upgrade itself without asking, that's when I make it go away.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-