Also fixed is this 7-year-old bug that has annoyed me for years: https://bugzilla.mozilla.org/show_bug.cgi?id=254714 (When you open a link in a new tab, the new page's URL doesn't appear in the Location Bar until the page loads.)
Until that's resolved, all the fancy CSS tweaks in the world won't mean a hoot.
It's much faster than the bloated beast that is Acrobat, but I'd say about 20% of the documents I open in Preview have to be viewed in Acrobat to be usable, so I've just defaulted to avoiding Preview instead.
A good, fast PDF viewer in the browser would be far better than either of those options.
Plus Preview can also do some very handy basic editing (cropping, adding/deleting/reordering pages, etc.), which I can only assume Adobe have left out to in order to up-sell you Acrobat.
It's already sandboxed and pretty fast and light-weight, so I'm not sure the Chromium developers would put much work into a replacement.
I'm currently running FF 3.6 on OS X. Getting regular announcements of 4.0, and thinking I'll install it sometime soon. I don't usually pay much attention to what features/problems the new version might have. So, what's up with this?
I mean they don't have to promote it through their website, just put it on the ftp. Take advantage of the dev-channel for some testing.
Yeah, I know, I don't need Flash ...
I wonder if Google is now committed to never break the Eextensions API now. To their credit, Android has done a great job with API compatibility over versions, not breaking old apps. Maybe Chrome can too, and dropping version numbers has raised the bar for software quality, just like forcing auto-upgrades has.
The whole thing is a bit silly.
This post composed in emacs 23. (Not really)
I guess Google is lucky/smart because Chrome extensions are juiced up user scripts with no native code (I think?), but FF needs to do something to save old extensions.
Version-less updates of browsers makes sense, and they should be seamlessly, silently, updated in the back-ground. This is getting crazy.
I install Firefox for friends and family who I want off IE, and this actually embarrasses me a little. If I have to keep telling them to update, they will quit - or end up using REALLY OLD versions of Firefox and we'll have an IE6 situation all over again soon but with Firefox.
I'm starting to install Chrome now. At least I can say that their browser will always update, and they have nothing to worry about.
The upgrade to 5 isn't much different than going from 3.8 to 3.16. Mainly, they've changed their numbering scheme, so there's no reason to make a big deal about it.
Here's the about Firefox dialog http://i.imgur.com/cDbN1.png and the update request http://i.imgur.com/4SYRI.png
That's not to say I don't see the allure of automatic updates, but I just don't want them to be silent and mandatory.
EDIT: also, the bash script is there because I install Firefox to /usr/local, and it's easier to type "update-firefox" in an already-open terminal than to reboot Firefox as root so it can modify my files. I'm aware it's redundant, but it also a) requires my active participation, so I can't miss it and b) lets me downgrade, in case of something like what happened above.
Who care's if Mozilla has more extensions? They cause too much trouble when you upgrade.
I do. TreeStyleTab and Pentadactyl essentially change Firefox into a different browser that I much prefer. There's nothing like that on Chrome, and until they get better capabilities for extension writing, there won't be. The day when they have working full replacements (not Vimium and the mediocre sidetabs option), I'll happily switch to Chrome, but until then I'll take having my nice customized browser.
Exactly. I switched to Chrome because of this and Chrome's better (less buggy!) Sync features.
Bugs like what you saw are flagged as high-importance "data loss" bugs, and FF has gotten better about avoiding those, even in pre-release builds, since the bad old days of accidentally deleting non-FF data from your home folder.
They were unstable, but I never corrupted my profile.
Just thought I'd report that for my (somewhat meager) selection of addons, I haven't found anything auto-disabled or crashing yet.