| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This should have no user-facing impact.
|
|
|
|
Move normal mode and its commands out of vimium_frontend.coffee
|
|
This makes the UI for generating an options backup the same for FF and Chrome.
We populate the *Backup* link on `mousedown`.
|
|
On Chrome, this text was becoming visible when the "Create Backup"
button was pressed.
Mention @mrmr1993: you might want to check this in FF.
|
|
Firefox doesn't seem to respect the |download| attribute for links, and
it garbage collects our blob URL when we navigate away from the options
page (to the object URL). We work around this by simply showing the
download link in Firefox.
Disappointingly, the user needs to right-click the link and choose to
download from the context menu.
Behaviour in Chrome is unchanged, except that the download link is now
visible.
|
|
See the *very* bottom of the options page (below advanced settings).
Clicking "Backup" creates a JSON file.
Selecting a backup populates the options inputs, the user then clicks *Save Changes* to confirm.
|
|
|
|
|
|
Changed "Treat find queries as regular expressions" to "Treat find queries as Javascript regular expressions", to reduce confusion. There are tonnes of different types of regular expressions, so specifying what type of regular expressions is used, will reduce confusion.
|
|
|
|
|
|
Updating URLs to use HTTPS provides greater privacy and reduces the
potential of having content modified whilst in transit (as it happening
more and more by ISPs, networks, state actors etc).
These URLs themselves have been tested and confirmed to work over HTTPS.
|
|
|
|
This reverts commit d00345f45b5b3e56970237799c69808527e91919.
This is not (and will not be) supported by Firefox.
|
|
This is one approach to fixing #2277 properly. (Currently there's a
temporary fix in place.)
This uses HTML5 imports in place of the content-script loader.
This is better than the current "fix" because content scripts are only
listed in one place two places (as opposed to six).
It's worse than the previous content-script loader, though, in that
content scripts must be listed in two places, instead of one.
Fixes #2277.
|
|
Follow on from 8601edd71e74ba522e32658309cb2e7acca8aeeb.
|
|
Scripts loaded via the content-script loader previously were loaded
synchronously. In recent versions of Chrome, they now seem to be loaded
asynchrnously, which causes errors.
This is a temporary commit to keep master healthy until I (or somebody)
figures out properly what is going on.
It is expected to be reverted in due course.
|
|
|
|
This makes the `hideHud` option apply only to insert mode (when entered with `i`).
Fixes #1953.
Fixes #487.
We could rename the option itself and add migration code, but that seems overkill.
An alternative would be to remove this option entirely.
|
|
|
|
|
|
|
|
|
|
Conflicts:
background_scripts/completion.coffee
background_scripts/completion_engines.coffee
|
|
See newly-added long comment for details.
|
|
|
|
Move "show-advanced-options" to a fixed-position button.
|
|
Instead of directly accessing the background page's Settings object,
the options page and the page popup now have their own.
|
|
This option is no longer needed, since we don't do search completion
except for custom searches.
|
|
|
|
|
|
|
|
|
|
- Fix incorrect camel case in option name.
- Better text on options page.
- Loud comments re. using option directly from chrome.storage.sync.
|
|
- add new option "GrabBackFocus"
- use chrome.storage.sync.get() to get option value
- avoid race conditions on load
- fix tests
|
|
https://github.com/smblott-github/vimium into smblott-github-search-engine-descriptions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 5ec7f490b5e9e68bddb415b66b6cae86841a3d52.
|
|
See #1299 for context.
|
|
|
|
IMO the default styling looks a lot better, at least on OSX
|
|
Conflicts:
pages/options.html
|
