| Age | Commit message (Collapse) | Author |
|---|
|
document.body.
|
|
This is a simple solution to #2832 that explicitly sets the background of text input and textareas to white on the options page, which is necessary for users running with a dark theme. This does not cover the options popup.
|
|
From URL:
http://[fe80::cce4:1680:e720:eacb]:8080/index.html
generate:
https?://\[fe80::cce4:1680:e720:eacb\]:8080/*
in the popup (note that [ and ] are now escaped).
Fixes #2967.
|
|
|
|
It's slightly strange how the classes and objects are structured in the
Vomnibar.
However, this refactors the code for launching URLs (including
Javascript URLs) such that we're not repeating the logix in two separate
places.
|
|
For example, search the current site:
cd: javascript:location='http://www.google.com/search?num=100&q=site:'+escape(location.hostname)+'+%s'
Apparently an example like this has been on the Wiki for four years, but
it has not been supported.
However, the change is so trivial that it's worth doing anyway.
Fixes #2956.
|
|
Follow on from #2750.
Specifically, the backup/restore functionality should be part of
"Advanced options".
|
|
Proposing this as a simpler alternative to #2934. Additionally, this
puts the logic for fixing #2915 in a single place.
Credit to @regmarmcem for figuring out the source of #2915.
Mention @regmarmcem.
Fixes #2915.
Replaces #2934.
|
|
This should fix an IME status issue (#2924).
|
|
Fixes #2876.
|
|
|
|
Put the version number in the popup.
|
|
To test the difference:
* load an unblocked URL (e.g. https://www.example.com) in a tab
* open the popup, see that the exclusion rules show as expected
* navigate the tab to a blocked URL (e.g. chrome://extensions)
* open the popup again
Before this commit, the popup still shows the exclusion rules, because
there is still a portForTabs object associated with the tabId.
This commit adds a second check to see if the object is empty, and the
message shows as expected, because all of the ports have been closed and
cleared from the object.
|
|
|
|
On pages where the browser does not run extensions like vimium,
replace the popup with a note explaining what and why.
Fixes #2850.
Currently, this is unsatisfactory because, on the Chrome new tab page,
Vimium does not become active until the user tabs or clicks into the
page (which is weird).
|
|
This was generating a (harmless) error on the popup page.
|
|
Tweak of #2601.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This should have no user-facing impact.
|
|
|
|
Move normal mode and its commands out of vimium_frontend.coffee
|
|
Some the long-reach code here is ugly. Things are too spread around.
This refactors the code called on "save" to a callback. Thus, the code
related to backup and restore is localised.
|
|
It's just cleaner this way.
|
|
In the case of exclusion rules, we first have to remove existing rules;
otherwise, the restored rules are *appended* to the existing rules.
|
|
This can be shorter now.
|
|
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.
|
|
|
|
|
|
Fix the popup dialog
|
|
DOM utils are required to inject user CSS.
|
|
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.
|
|
|
|
From a FF extension reviewer (gatekeeper) on Mozilla add-ons:
Comments:
Thank you for your contribution.
Please note the following for the next update:
1) For inserting text, textContent (or JQuery text) or createTextNode() should be used instead of innerHTML.
eg: $("saveOptions").innerHTML = "Save Changes";
So, here, `.innerHTML` is replaced with `.textContent` for elements
which only ever have text content.
|
|
|
|
|
|
|
|
|
|
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.
|
|
@mrmr1993: This is trivial fix for Firefox, so it doesn't warrant a PR.
I'll mention you just to keep you up to date on commits like this,
though.
|
