Hey, when did Mozilla get fixed?
I haven't used it in ages because forms didn't work, just uninstalled it and installed the latest (25) tried it and it seems to work with forms just fine. I'll have to test it long term to see it never glitches ever, but it does appear to work now. Finally. At freaking last. Good job.
The reason this is important is, if you can't go back and have your form data preserved, then you cant use this to edit anything on the web.
Let me say that again: you can't use it to edit anything on the web.
Ie, you've broken a LOT of web apps. To be sure, sites that rely only on Ajax won't see this as a problem, and that's why Chrome has got away with it for a long time - most of Google's stuff is Ajax. So if you want a browser that works well in the Google ecosystem, use Chrome.
But if you want a browser that works with ANY web app, you have to use Opera. And, it appears, now you can use Mozilla as well.
You know, I can actually live without V8's superior performance. I can actually live without WebKit's better rendering.
But If forms don't work? I can't use it.
Sorry. I'd rather it looks shitty and be slow that not work at all.
Ok, so, the video to demonstrate this concept. It's really not hard and you could have cobbled up a test in 30 seconds, but ok, I'll explain this slowly.
Here's Opera 12 doing this flawlessly.
What you'll see it a bunch of check-boxes get ticked and text gets entered then the home button is clicked to go to a differrnt page.
Then go back.
You'll see everything is in the correct state.
Then "reset" is clicked and everything goes back to the way it was before, when the page was loaded as is proper.
Without these two properties, you're not a browser that can be used for serious work. You can *get by* without the second one, bu the first is a show stopper, it means you can't edit anything on the web. And that's kind of a big deal.
These are straight off my (experia) phone so some people may have codec problems an they're shaky as it's hard to hold the phone, read and type and click mice and there's a goodly portion of thumb in one, but you can get the point.
Here's Opera 17 failing in the same way Chrome does.
Here's Chrome failing in the same way Opera 17 does. But at least Chrome has a home button.
Don't get me wrong, my preference is to use Opera, period. And I understand what a big deal swapping out presto and swapping in webkit is, but I think that's what has to be done to do this properly. Just recompiling Chrome and putting a red O on it means you inherit the Chrome bug-set. And these are non-trivial and profound: memory and spell-check for starters. Screw that noise, that's why I use Opera, cause stuff works.
Call the recompiled-chromium thing Opera Home and keep the legacy 12-branch Alive and phase WebKit in slowly and carefully. Strip it down to only the browser! No irc/torrent/unite/turbo - strip all that crap out - that just causes windows/osx/unix to swap-thrash anyway and stick to core browser functionality, do it right and call it Opera Pro.
I think you're going to find it would be easier to put webkit and v8 into 12 than to bring 17 up to date with 12's ergonomic features and get rid of the chrome bugs 12 doesn't have. While the legacy opera can be a petulant teenager, she is 15 but generally wall mannered and very stable now, but chrome is barely out of the terrible twos and still acts like it. Quite a contrast to the efficient and stable mature Norwegian codebase we've come to rely on.