462867 - keyword.url not saving changes

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[chrisrex1972]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

Just last week I learned the old default feature for typing in a word in the address bar had changed.  I liked the old system better where if I typed in the name of a store it just sent me to that store's website than the new default which sends me to a search results page. I learned how to change this by going to about:config and changing the keyword.url value.  I learned what the old default was and set the value to that.  However, it doesn't save.  I find that if I close Firefox it goes back to the new defaults instead of the one I overrode it with.  I am not sure why it won't save but I would like the value that I place in keyword.url to stay.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I tested this and it works fine for me.
Please read: http://support.mozilla.com/en-US/kb/Preferences+are+not+saved

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.