| Age | Commit message (Collapse) | Author |
|---|
|
Conflicts:
background_scripts/completion_engines.coffee
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This revamps how search-engine configuration is handled, and revises
some rather strange legacy code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If we have a custom search engine with a completer, then exclude
suggestions from other completion engines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This eliminates the need to repeatedly install and remove listeners for
@filterPort in the vomnibar. It also eleiminates the need for
"keepAlive" in reponses. All as suggested by @mrmr1993 in #1635.
|
|
|
|
|
|
Add plumbing to allow the front end to directly inform completers when
the user is typing.
|
|
|
|
|
|
|
|
|
|
|
|
Highlighting the search terms suggests they are in some way contributing
to the match. They are not, so don't highlight them.
This gets particularly ugly when you have short, single-letter costom
search engines (eg. w), and have all of the "w"s highlighted -- for not
useful reason.
|
|
This may or may not be a good idea. It means that the first completion
is just a tab away.
|
|
These should be removed later.
|
|
|
|
|
