Closed Bug 190468 Opened 23 years ago Closed 23 years ago

Regression: Type Ahead Find Autostart pref has become unset

Categories

(Firefox :: Settings UI, defect)

x86
All
defect
Not set
minor

Tracking

()

VERIFIED FIXED

People

(Reporter: davidpjames, Assigned: bugzilla)

Details

With bug 189228 type ahead find ceased to work until that bug was fixed. However, now that it is working again one can no longer find a link simply by typing; one has to use / or ' first instead, indicating that the pref accessibility.typeaheadfind.autostart has probably become unset from its previous setting to which Phoenix users are accustomed. There are two easy workarounds to reenable the prior behaviour until this is fixed: 1. open up or create user.js in profile directory with bookmarks.html, etc and enter the following: user_pref("accessibility.typeaheadfind.autostart", true); 2. -open a new tab or window and type "about:config" into the location bar -right-click anywhere and select "New" -the name of the pref is: accessibility.typeaheadfind.autostart -the value of the pref is: true
Sorry, to use the second workaround you want to select "New" and then "Boolean"
Additional comments in bug 189288 since I filed this bug indicate that this problem is present in Mozilla as well, but there there is an easily accessible pref to fix this that is not present in Phoenix.
Oops, that should have read bug 189228 in my last comment. Sorry for the bugspam.
More info: this was apparently caused by a checkin for bug 176296, where a new pref, accessibility.typeaheadfind.autostart, was introduced.
wouldn't the solution to this be to add: pref("accessibility.typeaheadfind.autostart", true); to the all.js file?
Technically, it didn't get unset. We just never required that pref before, because there was no way to turn autostart off in the past. Also, type ahead find is only the coding name now. The name for end users is now "Find as you type" -- at least for commercial Netscape. Do what you want for Phoenix.
Bryner just added the pref in all.js.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.