Browser.urlbar.matchOnWordBoundary: Difference between revisions
No edit summary |
(Replaced by browser.urlbar.matchBehavior) |
||
Line 6: | Line 6: | ||
Due to the amount of information available when searching those sources, it’s easy to come across cases where [https://bugzilla.mozilla.org/show_bug.cgi?id=404261 typed text will match useless items] (e.g., typing “ebay” might bring up a match for “thepiratebay”). To address this, word boundaries are taken into account when searching for matches, making text that matches against the start of a word rank higher than text matching inside a word (e.g., “eb” matching “ebay” over “website”). | Due to the amount of information available when searching those sources, it’s easy to come across cases where [https://bugzilla.mozilla.org/show_bug.cgi?id=404261 typed text will match useless items] (e.g., typing “ebay” might bring up a match for “thepiratebay”). To address this, word boundaries are taken into account when searching for matches, making text that matches against the start of a word rank higher than text matching inside a word (e.g., “eb” matching “ebay” over “website”). | ||
This preference | This preference determined whether or not to use word boundaries when searching for items in the Location Bar. It has since been obsoleted by [[browser.urlbar.matchBehavior]]. | ||
==Possible values and their effects== | ==Possible values and their effects== | ||
Line 18: | Line 18: | ||
==Has an effect in== | ==Has an effect in== | ||
* Firefox (nightly builds | * Firefox (nightly builds between 2008-03-18 and 2008-04-23; 3.0b5) | ||
==Related bugs== | ==Related bugs== | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=393678 Bug 393678 - location bar autocomplete should take word boundaries in account] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=393678 Bug 393678 - location bar autocomplete should take word boundaries in account] | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=429531 Bug 429531 - Location bar should show non-word-boundary matches below word-boundary matches] | |||
==Related preferences== | ==Related preferences== | ||
* [[browser.urlbar.filter.javascript]] | * [[browser.urlbar.filter.javascript]] | ||
* [[browser.urlbar.matchBehavior]] | |||
* [[browser.urlbar.maxRichResults]] | * [[browser.urlbar.maxRichResults]] | ||
* [[browser.urlbar.search.chunkSize]] | * [[browser.urlbar.search.chunkSize]] | ||
* [[browser.urlbar.search.timeout]] | * [[browser.urlbar.search.timeout]] | ||
[[Category: | [[Category:Unused preferences]] [[Category:Location Bar]] |
Latest revision as of 19:32, 24 April 2008
Background
In Firefox 3, the Location Bar received a number of improvements. Among those improvements was the move to a XUL richlistbox widget for the auto-complete dropdown. This allowed styled URL/title information, favicons, and highlighted match information. Typing in the Location Bar will now search not only URLs, but page titles, bookmark names, and tags.
Due to the amount of information available when searching those sources, it’s easy to come across cases where typed text will match useless items (e.g., typing “ebay” might bring up a match for “thepiratebay”). To address this, word boundaries are taken into account when searching for matches, making text that matches against the start of a word rank higher than text matching inside a word (e.g., “eb” matching “ebay” over “website”).
This preference determined whether or not to use word boundaries when searching for items in the Location Bar. It has since been obsoleted by browser.urlbar.matchBehavior.
Possible values and their effects
True
Use word boundaries when searching for typed text in the Location Bar autocomplete. (Default)
False
Search anywhere within available text, irrespective of word boundaries.
First checked in
Has an effect in
- Firefox (nightly builds between 2008-03-18 and 2008-04-23; 3.0b5)
Related bugs
- Bug 393678 - location bar autocomplete should take word boundaries in account
- Bug 429531 - Location bar should show non-word-boundary matches below word-boundary matches