| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | Refactor code for selecting the tabs to which a tab command with a count
prefic should apply. | 
|  | 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. | 
|  | According to:
  - https://bugzilla.mozilla.org/show_bug.cgi?id=1253129
and #2896, this:
1. causes Firefox to crash, and
2. isn't actually necessary.
So just remove it.
H/t @ris58h in #2896. | 
|  | Move the `reload` command to the background page and make it accept a
count prefix.
Fixes #674.
Althought the demand for this is low and the use cases limited, it is a
very vim-ish extension to the existing command. | 
|  | tabConfig doesn't exist in this scope. | 
|  | On the options page, treat all user-defined mapping commands as lower
case.
Why?
- `unmapAll` is not very vim-ish, and is inconsistent with `mapkey`.
- If we were to introduce `vmap` for visual mode, then we would get
`vUnmapAll`, which is hideous capitalisation.
Possible down side?
- I guess somebody might have disabled a `map` by capitalising it. | 
|  | Specifically, fix createTab with multiple URLs specified.
Fixes #2868. | 
|  | This puts link hints frame behaviour back to matching
fb00eaa6bd4ee8889d10a9ef9d976fefd3be7879
In particular, we go back to not sending link hints messages to frames
that are too small (according to DomUtils.windowIsTooSmall). | 
|  | This is a more complete fix for issue #2125. | 
|  | 43c7390f987fea063e7a97cd8b37c7b61d45f615 inadvertently broke link hints.
Mention @mrmr1993. | 
|  |  | 
|  |  | 
|  | Added UpToDate autocompletion engine | 
|  | These are no longer needed following #2601.
@mrmr1993... If these are ever needed again, then we can just revert
this commit (and make them background commands again). | 
|  | Tweak of #2601. | 
|  | Enable Firefox clipboard commands | 
|  | Examples:
    # Just create new windows
    map X createTab window
    map X createTab incognito
    # Create windows with URLs
    map X createTab window https://developer.chrome.com/home https://github.com/philc/vimium
    map X createTab window URL1 URL2 URL3
`2X` creates two new windows, each with all of the indicated URLs.
Fixes #2825. | 
|  |  | 
|  | This should have no user-facing impact. | 
|  |  | 
|  |  | 
|  | If
    map <c-[> someCommand
is configured, then the hardwired `<c-[>` meaning `Escape` behaviour is disabled.
Users who want to map `<c-[>` probably *never* use it as `Escape`.
Fixes #2722. | 
|  |  | 
|  |  | 
|  |  | 
|  | Search completion; add support for Google.co.jp completion | 
|  | Inject user css into all frames | 
|  | This fixes #2594. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | This also stops the content scripts from being injected into each frame
on reload (in Firefox only). They do not successfully connect to the
background page, and it causes considerable lag, so we lose nothing by
doing this. | 
|  | 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. | 
|  | The problem is that Firefox balks at function properties within the
response sent via `postMessage` (whereas Chrome does not).
A concise and safe way to sanitize the response is to convert it to JSON
and back.
Fixes #2576. | 
|  | This stops |Exclusions| from holding a reference to the |value|
parameter passed to |Settings.set|. In Firefox, this object is garbage
collected when the owning context (the exclusions popup) is closed.
The fix for all such cases in the future is to switch to using
|Settings.get|, which implicitly does |JSON.parse JSON.stringify value|
and thus returns an object in the same context as |Settings|.
We could fix this generally by doing this for the
|Settings.performPostUpdateHook| call in |Settings.set| instead.
However, I'm not convinced that it warrants the overhead of a
|JSON.parse| for every |Settings.set| call. | 
|  | Firefox baulks at "about:newtab" in createTab (but seems happy with no
URL specified).  Chrome is also happy with no URL specified.
(Does this mean that we don't need "about:newtab" ANYWHERE in the code
base?  Could Settings.defaults.newTabUrl just be ""?)
Mention @mrmr1993. | 
|  | This causes `o`/`O` to crash (producing no suggestions).
As a workaround, set any such title to "". | 
|  | Improve firefox support | 
|  |  | 
|  |  | 
|  |  | 
|  | The documentation suggests that 'highlighted' is equivalent to
'selected'. However, multiple tabs can be highlighted in a window -- in
fact, everywhere 'selected' was used, we wanted the unique active tab. | 
|  |  | 
|  |  | 
|  |  | 
|  |  |