| Age | Commit message (Collapse) | Author |
|---|
|
This sounds like #2035, #2305 is unrelated.
|
|
Do not open tab for target "_blank".
|
|
|
|
... use literals instead.
For some reason, on Firefox, using `vimiumOnClickAttributeName` was
causing link hints to fail silently (on Facebook). It's not at all
clear why this was happening.
Simply repeating the literal fixes the issue.
Fixes #2879.
|
|
|
|
This tweaks the scoring of hints for filtered hints.
Specifically, it scores matches at the start of the text or the start of
a word higher than whole-word matches.
This is intended avoid the phenomenon whereby adding matching characters
to the filter causes the selected hint to change.
|
|
Fixes #2860. That issue reports that, when the target is "_blank",
Firefox/Vimium ends up opening two tabs.
|
|
Since these are executing in the page's context, they could break the
page if they were to fail (for whatever reason). So we add some
(possibly unnecessary) guards, just in case.
|
|
Fixes #2876.
|
|
We should rotate on `<Shift-Space>` too.
|
|
|
|
This warrants a bump because 14f755cecdd548ba9fb82a04d3b708c75982a786 is
a serious bug.
|
|
This omission was causing link hints not to work on Google's Inbox (and
presumably elsewhere, too).
|
|
Treat all mapping commands as lower case.
|
|
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.
|
|
After merging #2870 and #2871.
|
|
Detect click listeners for link hints.
|
|
Include the Vimium version number in the popup.
|
|
|
|
|
|
`forTrusted()` for `checkEnabledAfterURLChange()` after web navigation
is being called with a request (not an event). So make the request
trusted.
The symptom was that pass keys and the enabled state was not being
correctly updated on web navigation.
|
|
This is a simpler version of #1167. It detects clickable elements with
listeners added with `addEventListener()`.
It includes some of @mrmr1993's ideas from #1167 (in fact, it's mostly
those ideas tweaked into a slightly different form).
|
|
Put the version number in the popup.
|
|
|
|
|
|
Specifically, fix createTab with multiple URLs specified.
Fixes #2868.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add "swap" command option for marks.
|
|
|
|
|
|
|
|
No clipboardWrite permission for Chrome Store version.
|
|
Small tweaks for popup message code
|
|
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).
|
|
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.
|
|
This is a more complete fix for issue #2125.
|
|
|
|
43c7390f987fea063e7a97cd8b37c7b61d45f615 inadvertently broke link hints.
Mention @mrmr1993.
|
|
|
|
|
|
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).
|
|
Recurse an arbitrary depth into shadow DOMs for insert mode element
|
|
|
|
Rework insert mode (check status dynamically).
|
