417213 - browser.urlbar.richResults is now being ignored

Status: VERIFIED INVALID

(Firefox :: Address Bar, defect)

Description

[FX]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3

With Firefox 3 beta 2, setting browser.urlbar.richResults to false allowed to avoid rich results (which slow the browser too much for my liking).  When I updated to beta 3, I discovered this is now being ignored.

Reproducible: Always

Steps to Reproduce:
1. In about:config, set browser.urlbar.richResults to false.
2. Type something in your URL bar, see autocompletion and rich text results.

Comment 1

[John P Baker]

see Bug 407836

Comment 2

[FX]

I'm not alone in asking that: http://groups.google.com/group/mozilla.feedback.firefox/browse_thread/thread/007f48a667be7748

And, by the way, the extension (Use this extension https://addons.mozilla.org/en-US/firefox/addon/6227) doesn't work on beta 3.

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified invalid.

Comment 5

[Topher Hunt]

From what I've read, this bug seems to be an intentional feature, and requests to restore the ability to disable rich results seem to be going unheeded. This disappoints me and I think that many Firefox users agree.

Comment 6

[Andrey Andreev]

Hi Topher,
Yes, this seems to be current attitude with Firefox 3.0. Removing and restricting existing functionality for no rational reason and despite objections is what has been going on with other features too, such as the "temporarily trust" button on the self-signed certificate warning popup, or the go-button quasi-removal, with no option to bring it back, or with the awesomebar. It seems to say - "yes, we know that you want it, and we know it is already there, but we know better, for we are cognitive scientists, and we're going to work hard to make it more difficult for you to do what we do not like." I am extremely disappointed with the 3.0 :(

Comment 7

[Topher Hunt]

Let's back up here. In many respects, I find Firefox 3 an amazing update - certainly speed and aesthetics are much improved, and I'm happy with most of the changes. Is there any good reason why Mozilla might prefer to enforce use of the rich bar as opposed to a basic bar? Also, perhaps the bug report site is not the best medium to discuss issues with Mozilla's philosophy / direction - if this issue amounts to such.

Probably the oldbar add-on will soon be updated to work with beta 4, providing a quick work-around for those of us who are unsatisfied with the default.

Comment 8

[Reed Loden [:reed]]

Seth, can you bump the maxVersion again?

Comment 9

[Seth Spitzer]

> Seth, can you bump the maxVersion again?

Bumped, but it might take some time before the change shows up on amo.

reed, thanks for the reminder.