That sounds like any firefox above 3.5.

i still got Firefox 3.5 installed just in case i need it.




that is the problem, i do like Chrome, well Iron, because it is fast, but i don't like the minimal look



Mozilla got a bit about that on their site and tell you why they changed it. I don't like it either, I wish it could be changed in chrome at least with firefox 4 you can change that.



Like the memory leak or have they fixed that at long last?

Is it not about time that problem was fixed?

Not normally, stuff normally gets added and you normally end up with a product that do everything even if you don't want it to.

Sadly with GUi they are going the other way, the way it is going the computer will be reading your thoughts to do stuff, because there will be no where to type anything into

They have not even fixed it in Nightly 6.0a1

So. As I said problems with FF4
If It aint broke, dont fix it !!!!

FF have had problems with memory leaks for years, it should been fixed years ago.
Instead of mucking about with the GUI which was fine, they should fix things that are more important.

As you say, I have read for a long time now that FF suffers memory leaks. But in all the time I have used it I have never encountered problems. What exactly are we talking here? The fact of the amount of memory used in use or the strict understanding of a memory leak insofar as FF not releasing that memory when exited?

If it's the first instance, I have not noticed any real difference in memory usage to Chrome or IE.

There is a blog which may go some way towards answering that.
http://blog.mozilla.com/nnethercote/...may-24-2011-2/
His other blogs are also worth a read imo. Interesting stuff. I hope he is getting the support he deserves.

I am absolutely fed up with Firefox v4 and 4.01. It is slow loading up, Firefox not responding and then crashing. I have just put v3.6.17 on and it is working great. I wish instead of mucking about with V5 why not get V4 to work properly.

There not just mucking with v5, they are up to v7 with the alpha builds

Another annoying thing about FF4
When I type a url in FF 3 location bar it takes me directly to the web site.
With FF4 I just get a list of possible sites found by Google
I cant be arsed with this
Dont tell me I can change things with about:config.
Why did this setting get changed ?

to make this clear. if you type bbc.co.uk into the address bar it does a search for bbc.co.uk ?

they didn't change that setting.

flagpole. I never mentioned the address bar.
Its the location bar thats the problem in FF4

I wouldn't read too much into it, they're just trying to de-emphasis version numbers like Chrome

You want this add-on to return it to normal.

switch to tab no more
https://addons.mozilla.org/en-US/fir...o-tab-no-more/


And 'address bar' 'location bar' are just different names for the URL box / bar.

Ant Video Downloader and Player Addon - Secretly collects data

A high-rated Firefox extension with more than 7 million downloads secretly collects data about every website the open-source browser visits and combines it with uniquely traceable information tied to the user, an independent security researcher said.

http://www.theregister.co.uk/2011/05...vacy_invasion/

Chrome uses the same system, I prefer it now, in fact going back to the old way is strange.

With chrome, when you start typing into the address bar it also looks in your bookmarks and give a list what it thinks you are looking for. if it can't find it, then it will go to your choice of search engine which for me is Bing.

The problem with the way Firefox done it was that it would always stick .com on the end.

It is getting to the stage where people are going to start getting worried about going online.

With all the hacking and all the privacy problems, the work i have done to get people on the net is being undone, because they read about these problems and get scared off.

i myself am considering not doing any shopping online anymore and if I do it will be with one of these pre-payment cards

I've gone back to 3.6 until they sort out 4 or 5. To be honest I've got IE9 as well and its pretty slick.

IE 9 is horrid, but then I never really liked IE to be honest. I tried IE9 for a day and that was enough.

I got firefox 3.5.19, but I only use it for some sites that for some reason don't like chrome.

Millions using the horrid thing then

http://en.wikipedia.org/wiki/File:We...sage_share.svg

You can revert this back to FF3 behaviour in the config page. I'll try to find the setting for you.

Given Mozilla claims all addons are security checked, doesn't it rather put a question mark over their checking process and the non-dodginess of potentially a large number of Firefox addons?

The thing is plugins can use their own web services to do anything they like and when making a HTTP request from a browser session will have all the cookies with it. How can you protect against that?

It was done then backed out for a hole new approach to Re-create AutoFill for fx5.

"Michael Ventnor 2011-05-26 09:12:56 PDT

No, the reason why I want to back this out is a) There are issues that I've caused that occur even with the pref turned off, and b) I have an idea on how to make this synchronous, but it will take a new approach and won't build on this code at all."

https://bugzilla.mozilla.org/show_bug.cgi?id=566489

"Peter Kasting 2010-09-19 16:56:38 PDT

Drive-by comment from the guy who designed and implemented Chrome's inline autocomplete based on my prior interactions with Firefox' browser.urlbar.autofill.

Inline autocomplete _must be_ synchronous. If it's not, where the user navigates is up to a race condition of "how fast you autofill" versus "how soon they press enter". This is frustrating enough to completely kill the feature. I highly doubt your infrastructure is set up to autocomplete synchronously; the entire address bar and history system for Chrome had to be purpose-built to make this happen.

Also, inline autocompletion must be predictable, learnable, and fairly stable. The whole point is to train users to hit a few keys and then enter as an accelerator for common URLs. If your ranking algorithms change what those keys autocomplete too, your users will become extremely frustrated.

In short, while this is incredibly useful, it is a giant minefield to get right. It took me probably nine man-months of effort to get most cases right in Chrome. IE9 is trying to do this and, from what I hear, getting it wrong; Safari has long tried to do this and gotten it very wrong."