| Age | Commit message (Collapse) | Author |
|---|
|
purpose and execution mode are more clear.
Sorry if you had patches in your local copies and this breaks them -- these renames were
a long time coming, and now is better than later.
|
|
|
|
|
|
|
|
vomnibar.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and doesn't work as well.
Now that Chrome saves your zoom settings, there's no need for our own zoom implementation.
This also fixes #370.
|
|
|
|
|
|
|
|
Conflicts:
commands.js
linkHints.js
vimiumFrontend.js
|
|
refreshing a tab breaks frame support because the framesForTab entry is appended with every onUpdate instead of being replaced.
|
|
problems for people.
|
|
|
|
|
|
tabs. This implements #274.
The motivation behind this change is that scrolling a page is far more common than
closing a tab, and so those actions should be on a hotkey which doesn't require a modifier.
Once you get used to scrolling without hitting ctrl, you won't be able to go back.
For existing users, this change also adds a custom mapping for them in their preferences to preserve
the old behavior as they upgrade from 1.21 to 1.22.
|
|
|
|
|
|
closes #284
|
|
options
|
|
|
|
|
|
|
|
(value 100). The shortcut combination is z0.
|
|
|
|
|
|
|
|
|
|
Conflicts:
commands.js
|
|
Conflicts:
README.markdown
background_page.html
commands.js
vimiumFrontend.js
|
|
and added 'q cmd' and 'q help cmd' to commands.js
|
|
box on the page.
|
|
on it.
|
|
Conflicts:
commands.js
|
|
I remapped toggleViewSource to 'gs' and set 'gf' to nextFrame.
Sorry this is such a huge commit. This is really the simplest way I can
find to allow the extension to track all available frames as well as the
currently-focused frame.
If Chrome would allow access to window.frames[i], then this could
probably be simpler.
|
|
respectively.
|
|
end of the page horizontally -- remove stylistic whitespaces
|
|
|
|
|
|
|
|
Conflicts:
commands.js
|
|
|
|
|
|
|
|
|
