Firefox 4 RC now available
blog.mozilla.com
blog.mozilla.com
1) Plug-ins like Firebug, web dev toolbar, greasemonkey, and resizeable textarea
2) Tabs are well-placed and readable, and you can simply double-click next to tabs to open a new tab
3) A proper status bar that's always visible
4) A full menu bar
5) No Adobe Flash built-in
I've installed Firefox 4 RC. The colors are loud. Tabs are on top, tab text is illegible, and double-clicking next to tabs doesn't create a new tab (it simply resizes the browser window). The status bar and the menu bar are gone. I couldn't even find Firebug and Greasemonkey.
Luckily, a few of these unfortunate decisions can be reversed. Apparently, you can turn on an "add-on bar" to show the controls for Firebug and Greasemonkey. You can also opt for a top menu bar, which has the added benefit that it re-enables the "double-click to create new tab" behavior.
IMHO, the new UI sucks balls. If Mozilla wanted to copy Chrome/Safari's UI, they've succeeded.
EDIT: After viewing some of my websites in Firefox 4, I must say that CSS3 and text rendering is a lot better than in FF 3.6. From what I can tell, it's on par with Chrome. I just wish it didn't have its UI as well.
Yes, it does, it's just a different mode of thought. Chrome is far less configurable than Firefox, and has some features than drive me mad - like the position of a newly opened tab.
They haven't succeeded because they still see the need for both a search box and an address box and the tabs don't close right under where the last close button was (my biggest gripes).
It's not really a fix, but as a less-aggravating workaround, you can use ctl-w or ctl-F4 to close tabs. That way you don't have to reposition the mouse every time you want to close a tab. And I can hit ctl-w with my left hand, so I still don't have to take my right hand off the mouse to use the keyboard shortcut.
2. (and this is the killer feature for me) If a particular search engine is selected (say, IMDB), I can right-click on any word on a page, and one of the context menu options is "Search IMDB for <selection>..."
Also, horizontal real-estate is not much of a concern on a wide-screen monitor - how much of the URL would I really want to see..?
Now maybe you're OK with that. But a lot of users are not (including non-technical users who don't even realize this behavior exists; once you explain what the unified bar does to them they become _very_ unhappy).
How is that a reason not to use Firefox over Chrome? Plugins can always be disabled, and if it's the principle of having proprietary stuff in your browser that you dislike, you can always choose Chromium, which doesn't include Adobe Flash or the PDF viewer, among other things.
After reading your comment, I have once again searched for a setting within Chrome to remove the built-in Flash, but I can't find it. That leaves Chromium and Iron.
The other issue I see is the the styling of the status bar, which seems incomplete. I added some additional styling to my userChrome.css and the bar now looks decent. (In Windows 7 with the Classic Windows theme.)
#browser-bottombox {
border-top-color: #808080 !important;
border-top-style: solid !important;
border-top-width: 1px !important;
padding-right: 16px !important;
}Is there anything compelling in Firefox 4 to get excited about?
I'd go a step further and say that now there are going to be an increasing number of Chrome users who will compare to Firefox 4 and want the performance and feature improvements that it has over Chrome and that may hold true for some time.
So, yes, you could look at it that way.
basically because of adblock plus and firebug i did newer jump on chrome bandwagon and i really like the firebox 4.
https://demos.mozilla.org/en-US/
There doesn't have to be only one browser, right? We want a few great implementations of the open standards.
In addition to all kinds of new HTML5 support, there's hardware acceleration, awesome SVG support, robust Audio API, and Panorama (press cmd+shift+e).
One other thing. It's small, and non technical, but I find I really like the very compact implementation of the pin tab feature. The way FF adds subtle indicators when the content on a pinned page updates is especially nice.
I'm on Chrome 10.0.648.127 and it does a periodic glow when pinned content has been updated. It's a little too subtle for my tastes, really.
2. Firefox Sync, which syncs bookmarks, tabs, passwords, history, and formfill data to all your different computers -- and to Firefox for Android. Firefox Sync encrypts your data client-side for privacy and security, and you can run your own sync server if you want to. (There are multiple open-source server implementations.)
Chrome 10 can encrypt everything client-side too.
http://www.google.com/support/chrome/bin/answer.py?hl=en&...
That does seem to imply that only passwords are encrypted while in storage. That's not surprising, since Chrome has a "master password" for password encryption, but unlike Firefox it does not require transferring an encryption key for your other sync data. (The client-side encryption key is the reason you need to "pair" your devices to set up Firefox Sync, instead of just entering a username and password.)
Sure! Here are some things I personally find exciting about FF4. I'm not saying everyone should find them exciting, they are just my personal opinion:
* FF4 is the only web browser to combine a tracing JIT with a method JIT for JavaScript. Some websites run amazingly fast with that. See the mozilla demos site for examples.
* IE9 has great hardware acceleration on Windows (but JS engine is inferior to FF4 and Chrome), while Chrome has a great JS engine (but hardware acceleration on Windows is inferior to FF4 and IE9), while FF4 is the only browser to have both great hardware acceleration on Windows + a great JS engine.
* Firefox is the only major browser that is 100% open source. (Chrome isn't open source, it bundles closed-source Flash and a PDF viewer as well as other stuff. Chromium is open source, but the vast majority of Chrome/Chromium users use Chrome.) Firefox is also developed in the open source way, completely in the open, unlike any other browser (including Chromium, where a lot of development is behind closed doors, then 'dropped' into the open - e.g., CrankShaft).
* Almost the same codebase used on desktop and mobile (mobile FF4 will hit RC very soon too). Opera has a mobile version, and Safari and IE have mobile versions too, but they are quite distinct. Firefox brings the mobile and desktop versions closer than those. Among the benefits is you can view desktop versions of websites in FF4 mobile very well. (Of course you generally want mobile versions of websites - but now and then, you do want a desktop version, especially on a tablet.)
You are right, if you are not hooked on some extensions chrome is a good option, my wife is a full time chrome user.
Extensions. Firefox has the greatest browser extension ecosystem bar-none. In the past, you had to choose between Chrome's performance, and Firefox 3's extensions.
Certainly Firefox was playing catch-up in performance, but we're there now. Chrome is still far far behind in terms of extensions, and showing no sign of catching up.
Simply put, Chrome extensions are HTML/CSS/JS, while Firefox extensions can actually manipulate the interface of the browser to a greater degree (making stuff like Vimperator possible when it wouldn't be possible on Chrome)
* Password manager with a master password.
* Different Awesome Bar behaviour (which some prefer to Chrome's)
* Delicious extension (the Firefox one blows away the Chrome one)... although that doesn't seem to work in 4.0 yet.
Until Chrome catches up to Firefox in features, I'm excited about a release of Firefox which catches up to Chrome in speed.
Chromium will use your native password manager if possible. For example on KDE it will use KWallet to store passwords.
Another thing, Firefox4 allows you synthesize audio in Javascript, something that Chrome (AFAIK) can't do yet.
On Ubuntu in particular (but on other Linux distros, too), Firefox 4 has a more platform-appropriate appearance and feel than the other cross-platform major browsers (Chrome and Opera).
For Web authors, there are more polished HTML5 form features to get excited about. For HTML5 feature involves new elements or attributes in markup, the chances of the features present in Firefox being polished is higher than the chances of the features present in Chrome being polished even though it might casually appear from html5test.com that Chrome support a larger number of these features. html5test.com tests if new APIs appear to be present--not if all the default user interaction works right or if the appearance of a feature is pretty across platforms (not just Mac and Windows but Linux, too).
The location bar history search in Firefox is remarkably more useful than in Chrome, because Firefox matches on more things than just the prefix of the URL (though Chrome has better search coming up and already available in about:flags).
Well, actually, syncing browsing history and passwords across browser instances in such a way that the data in encrypted and decrypted on your devices only is well worth repeating although it was mentioned already. (Syncing history and passwords is immensely more useful than just syncing bookmarks or sending over individual URLs, but history and passwords are the most sensitive browser data, so end-to-end crypto between the user's devices is important.)
(Disclosure: I'm consulting for Mozilla. Disclaimer: Speaking only for myself, though.)
https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
Will definitely continue testing it out.
https://bugzilla.mozilla.org/showdependencytree.cgi?id=59846...
For example, this bug significantly reduced memory usage, and was fixed less than a month ago:
https://bugzilla.mozilla.org/show_bug.cgi?id=631951
However, there are many memory vs. speed trade-offs in software, and as memory continues to get cheaper, you'll likely see all browsers choosing to use more memory in order to run faster.
This is what I use to measure what I believe to be real memory usage for Chromium: https://gist.github.com/864606
def thread_low(t): return resident_set(t) - shared_set(t)
lowerbound = sum(map(thread_low, all_threads)) + min(map(shared_set, all_threads))
(Forgive the Python notation, it would actually be easier to express this using actual summations if I could draw freehand, but given that I can't, I figure code would be clearer.)For all threads in the process, we know that it must be solely responsible for its resident set minus its shared set. This already is a lower bound, but it ignores what is shared. We can increase (improve) this lowerbound a bit by figuring out what the smallest shared set among all of the threads is. If my thinking is correct, then we can be sure the total memory used won't be lower than this.
Emacs: Vim
I guess different browsers for different types of people. I still use Firefox on occasion but mostly as a runtime for Firebug. Otherwise, I switched to Chrome more than an year ago and haven't looked back.
Firefox: Emacs
Chrom{e,ium}: Vim
Ideally, a master password should be a requirement, or passwords should go in the keychain on OSX. Many, many Firefox users do not know about the master password, so if you can sit at their computer you can see their passwords. It's terrifying.
Why does Firefox allow this?
We can't prevent this from happening so we try to provide a good way for other software to do it, so they don't do it in terrible ways:
http://code.google.com/chrome/extensions/external_extensions...
This is a historical accident; only toy and mobile OSes have any sort of application-level access control.
Wrong, they can just add DRM.