Talk:Places:AutoComplete: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
Line 1: Line 1:
==Disabling AutoComplete==
==Disabling AutoComplete==
Consideration should be made for the user who does not want to see autocomplete results below the address bar. This is a relatively common request for users migrating from the Suite, where this is an option (a pref: browser.urlbar.autocomplete.enabled). Currently a rather [http://kb.mozillazine.org/Disabling_autocomplete_%28Firefox%29 ugly hack] is required to accomplish this -- and the code matching against history still runs, just with no visible effect. If performance is already an issue taken into account when querying the history, this seems like a simple thing to check for first. --[[User:Unarmed|Unarmed]] 11:17, 4 Jan 2006 (PST)
Consideration should be made for the user who does not want to see autocomplete results below the address bar. This is a relatively common request for users migrating from the Suite, where this is an option (a pref: browser.urlbar.autocomplete.enabled). Currently a rather [http://kb.mozillazine.org/Disabling_autocomplete_%28Firefox%29 ugly hack] is required to accomplish this -- and the code matching against history still runs, just with no visible effect. If performance is already an issue taken into account when querying the history, this seems like a simple thing to check for first. --[[User:Unarmed|Unarmed]] 11:17, 4 Jan 2006 (PST)
Personally, I can't imagine this will ever happen.
-- Brett Wilson 16 Aug 2006

Revision as of 19:29, 16 August 2006

Disabling AutoComplete

Consideration should be made for the user who does not want to see autocomplete results below the address bar. This is a relatively common request for users migrating from the Suite, where this is an option (a pref: browser.urlbar.autocomplete.enabled). Currently a rather ugly hack is required to accomplish this -- and the code matching against history still runs, just with no visible effect. If performance is already an issue taken into account when querying the history, this seems like a simple thing to check for first. --Unarmed 11:17, 4 Jan 2006 (PST)

Personally, I can't imagine this will ever happen.

-- Brett Wilson 16 Aug 2006