| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
The UX around this is not quite right yet. It's better to disable it
for now.
|
|
|
|
Simplify front-end settings logic.
|
|
|
|
|
|
- Simplify the settings logic.
- Send a single request for all required settings (instead of 12
inidividual requests for the 12 settings values we need in the front
end).
|
|
|
|
We track the URL of the active frame in each tab so that we can
correctly populate the rules in the page popup.
Previously, we tracked URL changes only on focus events. This commit
moves that to isEnabledForURL, which is also called when the URL changes
as a result of web navigation.
|
|
|
|
smblott-github/mrmr1993-exclusion-rules-pushState-and-hash
Update exclusion rules when the URL is changed by history.pushState/popState or its hash changes (v2)
|
|
|
|
https://github.com/mrmr1993/vimium into mrmr1993-exclusion-rules-pushState-and-hash
Conflicts:
content_scripts/vimium_frontend.coffee
|
|
focus-main-frame-merge
Conflicts:
content_scripts/vimium_frontend.coffee
Also rework to remove dependency on Chrome 41+ sendMessage API
(specifically, relating to optional target frameId argument).
|
|
When the vomnibar closes, it focuses its enclosing window. If that is a
frameset, then we do not want to inadvertently register it.
|
|
Conflicts:
background_scripts/main.coffee
content_scripts/vimium_frontend.coffee
|
|
The event listeners were registered late, potentially allowing the page
to get priority over us for key events, etc., when:
* the original URL was disabled by an exclusion rule
* the URL was changed
- without a page load (by history.pushState or modifying
location.hash), and
- the new URL isn't (completely) disabled by any exclusion rules.
This forces the event listeners to be registered even when the
current URL is disabled, to avoid this problem.
|
|
|
|
Specifically, the
chrome.tabs.sendMessage(tabId, message, options, callback)
API doesn't exist before Chrome 41, instead taking the form
chrome.tabs.sendMessage(tabId, message, callback).
|
|
This uses the chrome.webRequest API to detect changes to page URL which
*do not* cause the content script to refresh.
|
|
|
|
1. Rework event handling to eliminate frame flicker (a la #1485).
2. Tidy up logic. Which should make this more robust.
|
|
Remove reference to unused setting "vomnibarInTopFrame".
|
|
This lines was never needed.
|
|
Show yanked text in HUD for "yf"
|
|
|
|
If the element does not have an HREF, then we shouldn't be offering to
copy it's link.
|
|
Note: We probably shouldn't be offering these links at all.
|
|
|
|
|
|
|
|
Fixes #426.
|
|
|
|
|
|
Conflicts:
content_scripts/vimium_frontend.coffee
|
|
|
|
|
|
Since the vomnibar now always is initialised and opened the top window
(see d67347461da5a0468547e4c807a54bb40746faf4), there's no longer a need
for this to be a Vimium Labs feature.
|
|
Vomnibar commands are handled in a frame even is isEnabledForUrl is
false.
|
|
|
|
|
|
|
|
Return to the original viewport (when no find matches)
|
|
smblott-github/selection-handling-on-exit-from-visual-mode
Tweak selection handling on exiting visual mode.
|
|
Add a "What's New?" link on help page.
|
|
|
|
|
|
When there is no find-mode match, return to the original viewport. This
is a better UX in visual mode, because the text the user is searching
for is often on within the viewport.
(This is also more vim like. We could consider *always* working this
way.)
|
|
Previously, we removed the selection on exiting visual mode. This
collapses the selection instead.
My own experience with visual mode suggests that this is better. In
particular, if we remove the selection, then when the user re-enters
visual mode, they're dropped into caret mode. It is unlikely that the
default caret position selected by caret mode is better than the last
text selected by the user in either caret mode or visual mode.
|
