Closed Bug 1514780 Opened 2 years ago Closed 1 year ago
Use the new tokenizer in Unified
Complete (to make restriction characters handling more consistent)
47 bytes, text/x-phabricator-request
|Details | Review|
For some reason restriction tokens are breaking the search, no results are returned when searching for "* moz" for example.
This is actually due to the different tokenizer we use in the new and old code, the new tokenizer considers "*moz" as a research on bookmarks for the word "moz", while UnifiedComplete considers it a search for "*moz". The best path forward would probably be to use the new tokenizer in unifiedcomplete, that is not exactly trivial, but it would allow us to hammer down some of its potential bugs.
Summary: Fix search with restriction characters → Use the new tokenizer in UnifiedComplete (to make restriction characters handling more consistent)
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/f2f4a6eb1576 Use the Quantum Bar tokenizer in UnifiedComplete. r=adw
You need to log in before you can comment on or make changes to this bug.