DownloadThe latest version of Firefox Beta has the following changes:
- [New] The forward button is now hidden until you navigate back
- [New] Anti-Aliasing for WebGL is now implemented (see bug 615976)
- [New] Full Screen APIs allow you to build a web application that runs full screen (see the feature page)
- [New] CSS3 3D-Transforms are now supported (see bug 505115)
- [HTML5] New element for bi-directional text isolation, along with supporting CSS properties (see bugs 613149 and 662288)
- [Developer] Inspect tool with content highlighting, includes new CSS Style Inspector
- [Developer] We've added IndexedDB APIs to more closely match the specification
- [Fixed] Some users may experience a crash when moving bookmarks (681795)
DownloadThe latest version of Firefox Beta has the following changes:
- [New] The forward button is now hidden until you navigate back
- [New] Anti-Aliasing for WebGL is now implemented (see bug 615976)
- [New] Full Screen APIs allow you to build a web application that runs full screen (see the feature page)
- [New] CSS3 3D-Transforms are now supported (see bug 505115)
- [HTML5] New element for bi-directional text isolation, along with supporting CSS properties (see bugs 613149 and 662288)
- [Developer] Inspect tool with content highlighting, includes new CSS Style Inspector
- [Developer] We've added IndexedDB APIs to more closely match the specification
- [Fixed] Some users may experience a crash when moving bookmarks (681795)
Check your fps in Chrome vs Firefox on this: http://ie.microsoft.com/testdrive/Performance/FishBowl/
Firefox is at 60 until 2000 fish, then its around 54~.Originally Posted by PoopaScoopa
Check your fps in Chrome vs Firefox on this: http://ie.microsoft.com/testdrive/Performance/FishBowl/
Not all synthetic tests are relevant to real world apps.
for me its 60fps even at 2k fish and I get 753174 points on that other test.(FF10)
Yeah, speed means nothing when you can't notice a difference without a benchmark. They are all sufficient in speed. The only reasons to even post or worry about those is to try to justify why you use one or another, or to try to sway someone else into using the one you do. Both are pointless. Use the one that has the UI and features/add-ons you like and be done with it. Most of those tests are heavily CPU dependent, so comparing one person's to another is pointless anyway. For reference, I got almost 750K on FF12a in the browser mark. Would I get more in Chrome? Probably. Would I notice any difference at all in every day things? 99% sure I wouldn't. I use FF because it has the things I like and I love the customization. For those who like to mess around with every little thing, FF is a must for a browser.
About:flags shows its enable. Even with 10 fish I'm getting 17 fps.