| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
"pages/blank.html" was being sent to the default search engine by
chrome.tabs.create().
Not fully functional. New tabs created from incognito mode are created
in a non-incognito mode window.
|
|
We should not inject content scripts on chrome upgrades.
|
|
|
|
This is @mrmr1993's work from #1041.
Reload content scripts when vimium is installed or updates.
(@mrmr1993: The automatic merge was really messy (or, at least, I
couldn't figure out what was going on). Since the bulk of #1041 was
actually quite compact, I took the liberty of just copying it in. Hope
you don't mind.)
|
|
This is a quick fix only (to keep master in a functional state).
openUrlInNewTab is broken, and needs to be refactored.
|
|
|
|
|
|
- This fix enables `2t` to open two new tabs, even in incognito.
Include callback in the call chain so that numbered commands can work.
|
|
Following on from c8d984520f5de4b3e702cee992c7ecc4f4f49435, I forgot to
fix up the other call to setBadge.
|
|
Fixes #1491.
|
|
- Change openUrlInNewTab to pass tab.windowId
Why? Work around for upstream bug #308171
- Change createTab to use openUrlInNewTab
Why? Fix issue #1507 to open new tab in current window
(Note: This commit removes noise from the code and explains the changes)
|
|
- Change openUrlInNewTab to pass selected tab.windowId
- Change createTab to use openUrlInNewTab
|
|
See #1495.
|
|
And, following on from 7a746ba51a5124a39acb09270bf4ab470bfd6b5f:
- 7a746ba51a5124a39acb09270bf4ab470bfd6b5f seems to work. However,
there's a slight unnecessary flicker when changing tab. So, this
tries *not* setting an initial icon, and waiting instead to hear
back from the tab.
|
|
Following on from 6d776a9f56f05e4298577f25f0a54b924cb1f6e6, I'm still
seeing issues with the browser icon showing disabled which Vimium is in
fact enabled.
I'm going to try this for a bit, and see if it fixes the problem.
|
|
Retain frame data for a tab unless the top frame tells us its closing
|
|
I'm seeing an intermitent issue whereby the browser icon is showing as
disabled, when vimium is in fact enabled. It's intermitent, so
difficult to track down.
I went back to look at the old code for setting the browser icon, and
reset this code to look more like the old code. I suspect the problem
may be that we disabling the icon because we're getting no response from
one frame (or something like that).
|
|
It seems this was probably used at some point before the introduction of
settings.set() in the front end. It isn't used at all, now.
|
|
|
|
|
|
Fix conflicts from 9f20c33adf75e2e78b35e2cd16f2a0925a72c577.
|
|
Conflicts:
background_scripts/main.coffee
|
|
Conflicts:
background_scripts/main.coffee
content_scripts/vimium_frontend.coffee
lib/keyboard_utils.coffee
|
|
|
|
Approach:
- We never save the find mode history from an incognito tab in the
settings, instead they are saved in the tabMapInfo for each
currently-active incognito tab.
- When a new incognito tab (or page, after navigation) starts, we
scan the tabMapInfo looking for the find-mode history of any active
tab.
In this way, the history is shared between incognito tabs, but discarded
once the last incognito tab closes.
|
|
|
|
|
|
The return value from copyToClipboard is passed to sendResponse by the
chrome.runtime.onMessage.addListener listener. This was using the
(somewhat arbitrary) value returned by Clipboard.copy, which turns out
to be circular, causing an error.
This fixes that.
|
|
The return value from copyToClipboard is passed to sendResponse by the
chrome.runtime.onMessage.addListener listener. This was using the
(somewhat arbitrary) value returned by Clipboard.copy, which turns out
to be circular, causing an error.
This fixes that.
|
|
- This commit is incomplete because, to progress, we need bc7db7473456713c8c84f324e71da93145ffa2a0.
|
|
- "dw", "3dw", "d3w"
- "dc", "3dc", "d3c"
- "D"
- "C"
Also refactor enterInsertMode.
Also major refactor of interface between edit and visual modes.
|
|
|
|
|
|
Slightly more significant:
Move several utilities to dome_utils.
|
|
- Add StateMode.
- PasskeysMode is a StateMode.
- BadgeUpdateMode is a StateMode.
- Improve badge handling.
- Add push method to Mode.
- Document how modes work.
- Cache badge on background page to reduce the number of updates.
- Remove badge restriction on document.body?.tagName.toLowerCase() == "frameset".
- Add ExitOnEscape mode, use it for ConstrainedMode and FindMode.
- Move PostFindMode to its own file.
|
|
|
|
|
|
|
|
|
|
As a proof of concept, this incorporates normal mode, passkeys mode and
insert mode.
|
|
|
|
From top to bottom on the diff:
- The echo handler on the background page is no longer required.
- Simplify/refactor vomnibarUI message handler.
- Initialise vomnibar query to "" (rather than null) and simplify.
- No need to focus parent window when vomnibar closes; that's handled by
the iframe framework. Also no need to blur.
|
|
Conflicts:
content_scripts/vimium_frontend.coffee
manifest.json
|
|
- Simplify component API.
- Iframe flashes on re-focus.
- Probably some other stuff which I've forgotten.
|
