Erm...
Should it not be Mozilla CSS Animation. Seeing as it does not work on another browser.
Are we going into the realms of MS inspired web browser design here?
(note the -moz on the css attributes)
Mozilla has released a public beta of Firefox 5, ahead of its planned final release in late June. The test build comes a month after Mozilla rejigged its browser release schedule in a clear nod to Google's Chrome. CSS animation is the big advancement in the next, lightly-developed iteration of Firefox. Additionally, the do- …
CSS Animations? I thought we got rid of the BLINK and MARQUEE tags.
Some sites already do these things in javascript
That's why I use QuickJava and keep it turned off.
I wish the development team would stop fooling with trivial crap. Give me a browser that is immune to malware, loads instantly, and doesn't use hundreds of megabytes of memory.
Sometime in the future on The Register:
Computer Git Mauled At Local Zoo
User thinks lynx a big pussy
Local computer nerd climbed into a zoo cage hoping to find a better browsing experience only to have his giblets minced by a lethargic Eurasian Lynx. The cage was strewn with abandoned iPhone 6s and various fondle slabs by would-be photogs and journos that had cheerfully wandered...
possible to mathematically prove that sofware is formally correct (i.e. has no implementation bugs), as was done for seL4 microkernel. If you can also avoid design bugs (not easy, but it should be possible to prove correctness with pen and paper), you can make software immune to malware of any chosen description.
You may smirk at something like CSS animations, but it *entirely* depends what they are used for!
It's the same as Flash - depends what it's used for.
Yep, there's countless cases of horrific content with all new browser advancements - in the same way there's countless crap websites. Heck, lets stop all color and images in browsers, because some sites abuse it!
I can think of many uses for CSS animations - interactive diagrams for instance. Graphs. Maps.
I really get irritated at knee jerk reactions like this, because it a clear case of failure to see beyond the end of your nose.
"Animated CSS will be used for crappy adverts, so it must be bad..."
*sigh*
Not at all. It's great news for everyone involved with web design and development. IE is still 5th best in a field of 5 though. The problem here isn't Microsoft at all, it's the know-it-all accountants and the odd BOFH that won't upgrade for frankly lame reasons; if your shite web app won't work on any other browser it's broken. Fix it and this time use standards.
between "competent product" (as in: something I can reasonably work with, if I have to) and "good product" (something I choose to work with when given few alternatives).
IE9 is - finally - a version of Internet Explorer that doesn't make me cringe every few seconds. It does however a quite few useful features, provided natively or with addons on Firefox & Chrome, which means I wouldn't choose to use it.
"The open source outfit's developers have in the past felt weighed down by version numbers of its browser"
I've always thought you could go to the release site and choose when to download the latest version.
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Personally I hang on until version 0.03 of the latest version. For those of you on the bleading edge there is always the nightly builds ..
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
"until you've done that don't blame the browser."
but when the same collection of plugins and addons all worked perfectly fine under the last version of FF then is it not safe to assume that FF broke something?
ff4 plays merry hell with my netbook, and I for one is not happy and is considering installing,,,, IE
- URL history - if you customized your settings, it can be really big and has to stay in memory for "awesome bar" to work - try decreasing the time for which it is stored and clearing it.
- add ons - make sure you get rid of skype toolbars, mcaffee site advisor and any such cr*pware
- flash - yep, it has memory leaks. install flashblock, see what happens.
Hm, something wrong somewhere else in your computer. Java? (I see CPU usage go crazy when some bad Java applet is trying to run)
As I type this, using FF 4.01 on Ubuntu 10.10, the System Monitor graphs on the panel say almost 0% CPU usage (out of a quad-core) and, clicking on it, brings up the details of the processes; FF is using 174 MiB of RAM (out of 6 GB). And it's been running for hours (although this Reg page is the only open tab right now).
Mind, I do have a few extensions and plugins installed, let's see... Zotero (plus Oo integration), AniWeather, Fast Dial, some orthographic correctors, Flash, Adobe Reader...
I must be lucky, I guess. My 2.5 year old netbook is also running FF 4, smooth as butter (also on Linux, of course).
Firefox 4 is buggy junk that freezes and crashes on a regular basis. I've uninstalled it and it and gone back to 3. It used to be good, now it is overbloated, believing its own bullshit type software that I would expect to come out of Redmond.
Why won't it load pages quickly like Chrome, and I hate Google too.
So far we've seen firefox, add-ons, and the user to blame for these memory leaks. How about the software that's downloaded from the sites you visit and run in the increasingly complex world that is the web browser's internal engines?
Just the other day on IRC I saw someone point out that use of the new fangled 'surface' API's available from many Javascript toolkits meant that memory was not being free'd properly. If a page is re-loaded many times, especially during development but quite possible during normal browsing, the memory usage increased to 1.5Gb fairly quickly.
Try typing "about:memory" into your address bar, and see if there are any obvious culprits. In his case, it was clearly gfx/surface/image : http://i55.tinypic.com/21461k9.png
I don't know who's actually to blame here, it could be the javascript programmer not freeing resources, the library designers not releasing references, the Javascript engine not garbage collecting in the way you expect, the browser for not, I don't know, being omniscient about the previous points, or something else entirely. My point is that it's not simple and we should stop pointing fingers in a kind of Mexican standoff (amusing though the mental image might be).
I make the distinction between the browser and the Javascript virtual machine within it for good reason, though some may disagree and consider them the same thing. Perhaps that would make it easier to blame 'Firefox' for the fault.