| Age | Commit message (Collapse) | Author |
|---|
|
Add CoffeeScript v1 requirement to CONTRIBUTING.md
|
|
|
|
|
|
|
|
|
|
Fall back to using event.key.
|
|
If `event.code` is not defined, then fall back to using `event.key`
instead.
Fixes #3099.
|
|
|
|
|
|
|
|
|
|
Site-specific hack to make expanded tweets scrollable.
|
|
|
|
Twitter is an important site and Vimium's scrolling is currently broken
when a tweet is expanded.
In my opinion, the existing bahviour is so bad and that a site-specific
hack is warranted.
Fixes #3045.
|
|
|
|
Refactor code for selecting the tabs to which a tab command with a count
prefic should apply.
|
|
|
|
|
|
Launching link hints can sometimes be slow. For filtered hints, the
user already knows what to type - but must nevertheless wait until the
hints have been calculated and rendered.
Here, we cache intervening keydown events, and replay them once
hints-mode proper is launched. This should make improve usability (in
the case of filtered hints).
Fixes #3050.
|
|
Fixes #3068.
|
|
Fixed frustrating IME leftover issue when press ESC in input
|
|
Issue #3054
|
|
replace \xA0 on copying and pasting
|
|
document.body.
|
|
|
|
|
|
Use hash (too) for local marks.
|
|
First, I *very rarely* use local marks. They just don't seem as useful
in a browser as they are in a text editor.
However, on a page like GMail, I do often want to jump back and forward
between my labels. These are different locations hashes (anchors).
The idea here is to make local marks useful for this case.
If the scroll positions (X and Y) are both 0, and the hash (anchor) is
present in the mark and non-empty, then change the hash instead of
scrolling.
On first tests, this appears to work nicely for changing labels in
GMail. I'm sure there are other uses.
This change shouldn't interfere with use cases where the user has
scrolled within the page.
|
|
|
|
Explicitly set background colour for input fields
|
|
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.
|
|
Escape [ and ] in hostname in 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.
|
|
|
|
Chrome has never searched in all frames, so this is no loss.
However, find on Firefox Quantum is now broken with the "all frames"
flag set.
Fixes #2962.
H/t: @gdh1995 (https://github.com/philc/vimium/issues/2962#issuecomment-367991086).
|
|
on FindMode exiting, blur input first
|
|
|
|
Apparently some versions of Firefox are baulking at unreconised
properties in the manifest.
See: https://github.com/philc/vimium/issues/2965#issuecomment-367659475.
Mention @KyleLS.
|
|
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.
|
|
|
|
smblott-github/javascript-URLs-for-custom-search-engines
Allow javascript: URLs for custom search engines.
|
|
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.
|
|
|
|
Fix Firefox link hints.
|
|
This was failing in iframes in Firefox (causing all sorts of other stuff
to fail).
|
|
|
|
Fixes #2958 (probably).
This appears to be correct for target "_blank" (or not) and modifiers
(or not). That's four cases.
It will be *incorrect* if there is a click listener on a target "_blank"
link. Some conditions are tested to try to prevent that from happening.
This only affects Firefox. Chrome is unaffected.
|
|
|
|
|
|
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.
|
