Read more.Just 5 weeks after Firefox 11
Read more.Just 5 weeks after Firefox 11
Hmm, still way behind Chrome, Chrome is like SIX better right now.
Wonder why they are still supporting XP SP1? As Sp3 is free to download the only people who would benefit is people pirating windows - why would they want to encourage that?
Here we go again. This is getting so tiresome. Can they really not produce a version that is stable and current for more than 10 minutes?
It is by design apparently that they're coming out with major version changes in such a stupidly short time frame. It seems crazy to me and it's a real problem at work - change control requires extensive testing before a major version change of pretty much anything can be rolled out and with workloads being what they are we're just about to approve version 11 when they release version 12.
Well that's almost 9 versions a year, they'll be at version 30 by mid 2014...
I think they need to switch to an Ubuntu style yy:mm scheme and do one every even numbered month or something, it's far more sensible and very quickly allows you to know how up to date a version is.
And this is the reason I have moved to Chrome, no major updates from Firefox, nearly all could have been point releases. And further to that and more importantly for me, addon's constantly breaking because the version number is different.
Not sure what Mozilla is playing at but its put me off Firefox.
Jon
The following maybe of interest to someone:
http://www.mozilla.org/en-US/firefox...ersion=rv:11.0
They still haven't found a solution to their flickering 'Firefox' and right click menu's. If they claim addons are to blame, then surely take out the loop hole for those Add ons to be able to cause it in the first place.
The menu flickering always happens to me as soon as the Aero performance dialog has been triggered by a game.
Very easy to re-produce :S
Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive
Far from the best place to post this, but you've just reminded me of a flickering problem in device manager which I can easily reproduce across machines. Basically just open Device Manager, then an item, say a network card, then hover over the X button which should begin to flicker.
Exactly, only thing I can't do is pin point the precise Addon/Extension doing it on mine. When I disable any of them, the flickering stops whilst Firefox is still loaded. Restart Firedox and the flickering starts again, so clearly not the one that I just disabled. OR it might be that all the addons I have are doing something incorrectly to Firefox's specification.
Last edited by AGTDenton; 24-04-2012 at 05:26 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)