| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
This prevents issues like #1731 and is an (better) alternative to #1732.
|
|
|
|
|
|
|
|
... for FindModeHistory.
|
|
|
|
|
|
|
|
|
|
|
|
This keeps searches with trailing spaces from missing matches where the
page contains normal spaces, preventing " (No matches)" being shown
every time space is pressed.
|
|
|
|
|
|
|
|
|
|
On that page, we have regular expressions (which are not new-user
friendly) and an example (which is new-user friendly). So the example
should come before the regular expressions.
|
|
Conflicts:
background_scripts/completion.coffee
background_scripts/completion_engines.coffee
|
|
This commit contains the bulk og the material changes for which the
previous commits established the basis.
1) Add a general framework for detecting query prefixes in search URLs,
adding them to query sent to the completion engine, and stripping them
from the resulting suggestions. This allows the user to have a
search engine...
j: http://www.google.com/search?q=javascript+%s Javascript
and have the prefix "javascript" included (automatically) in queries
sent to completion engines, which results in substantially better
suggestions.
2) Re-work completion for Google Maps in a simpler form.
|
|
The original completion-engine interface was based on three functions.
With some experience, it seems there is a pattern involving explicit
regular expressions which is used by all actual engine implementations.
This is a refactoring to make those regular expressions explicit (and
required), and is a first step towards adding additional fucntionality.
This also simplifies the completion cache key (use JSON instead of some
weird hash).
|
|
|
|
Instead of just giving an example search URL, we can give the actual
declaration (which the user can copy, paste and tweak).
|
|
This allows the user to copy and paste search URLs from this page into
the options page.
|
|
With this, if we're in custom search mode and the cursor is at the start
of the vomnibar input and the user types <Delete>, then we exit custom
search mode and reinstate the keyword (and arrange for the cursor to be
in the right place).
This makes it possible to change (or just disable) the custom search
engine without having to first wholly delete the query.
|
|
|
|
|
|
|
|
|
|
See newly-added long comment for details.
|
|
This is a minor re-working of #1705 from @mrmr1993.
The main changes are:
- Simplify initialisation logic.
- Always initialise Settings immediately and automatically (ie. don't
initialise Settings separately and manually in the background,
content scripts, options and tests).
- Get rid of addEventListener (it's only being used for on "load").
- Add Settings.use() in its place.
|
|
|
|
|
|
|
|
(This was supposed to have been removed previously. Oops!).
|
|
|
|
Move "show-advanced-options" to a fixed-position button.
|
|
Move Vomnibar commands to own category on help page.
|
|
Direct keyboard access to custom-search engines via keyword flag
|
|
The help page gets pretty lopsided when advanced commands are shown. This balances things out a bit by creating a new category for Vomnibar commands in the right-hand column.
|
|
Ass suggested in by @LarryBattle in #1643.
|
|
This avoids a flicker whereby the keyword is first inserted into the
input, then removed.
|
|
Instead of directly accessing the background page's Settings object,
the options page and the page popup now have their own.
|
|
completion-on-custom-search-only-merge
Conflicts:
background_scripts/completion.coffee
|
|
In omni mode, the vomnibar suggestions are updated asynchronously.
Therefore, the contents of the primary custom search-engine suggestion
may be behind the actual contents of the comnibar input. So, we
reconstruct the custom search-engine query on "enter".
(This fixes a long-standing race condition.)
|
|
This option is no longer needed, since we don't do search completion
except for custom searches.
|
|
|
|
Do not use tab-to-open the vominibar in tabs mode. (It doesn't make any
sense.)
|
