Simon Lydell [Sun, 15 Dec 2013 18:48:11 +0000 (19:48 +0100)]
Always open regular find bar, not last used
There are three find bars: The "regular" one, the "quick find" one and the
"quick find (link only)" one. Before, the VimFx `/` command opened the one
of those three that was used last. Now, the regular is always opened.
Simon Lydell [Sat, 14 Dec 2013 11:56:54 +0000 (12:56 +0100)]
Auto-focus findbar in find mode onInput
Now, if you unfocus the text input of the findbar, it will be
automatically focused again when you start typing. Before, nothing at all
happened (commands weren't run either), which felt really weird. This
reminds you that you're still in find mode, and need to press Enter or Esc
to exit from it.
Simon Lydell [Fri, 25 Oct 2013 16:48:56 +0000 (18:48 +0200)]
Fix #213: Suppress logic bug
For example, if you press 'x' to close the current tab, it will close
before keyup fires. So keyup (and perhaps keypress) will fire in another
tab. Even if that particular tab is blacklisted, we must suppress the
event, so that 'x' isn't sent to the page. The rule is simple: If the
`suppress` flag is `true`, the event should be suppressed, no matter what.
It has the highest priority.
Previously, `vim.blacklisted` checks were performed even in keypress and
keyup, which caused the suppress to be ignored.
Simon Lydell [Tue, 1 Oct 2013 11:35:13 +0000 (13:35 +0200)]
Make command_Esc in charge of all "escaping"
To be able to exit modes or blur text inputs, you _had_ to use Esc before.
It was hard coded. Now, changing the shortcut for command_Esc works as
expected.
Simon Lydell [Wed, 11 Sep 2013 20:24:01 +0000 (22:24 +0200)]
Let un-blacklist remove _all_ matching rules
Previously, only the _first_ matching rule was removed when the user
clicked the "un-blacklist button". But it would be a bummer if the user
clicks to remove the page from the blacklist, and it stays blacklisted.
Therefore _all_ matching rules are displayed and removed. To facilitate
this, the string in the textbox of the toolbar button is treated as a
blacklist of its own, which should be removed from or concatenated with
the blacklist pref. (Which means that the user is now able to add multiple
rules at the same time, should anyone want that.)
Simon Lydell [Tue, 10 Sep 2013 14:29:24 +0000 (16:29 +0200)]
Fix #190: Improve blacklisting UI
- Fix bug: on `about:` pages `**` was suggested as blacklisting rule
- On blacklisted pages, the blacklist button un-blacklists instead
- Live validation of the black list setting
Simon Lydell [Tue, 10 Sep 2013 10:40:34 +0000 (12:40 +0200)]
Fix #192: Clarify customization is in help dialog
- Add button in settings page to customize keyboard shortcuts (open the
help dialog)
- Change "Help" to "Keyboard shortcuts"
- Fix bug: Help dialog broke the layout in XUL pages
Simon Lydell [Sat, 7 Sep 2013 20:56:50 +0000 (22:56 +0200)]
Fix: Dropped out of insert mode on location change
For example, it would be nice to usually be in insert mode in gmail, and
only occasionally leave it. However, as soon as you for example went from
the inbox to an e-mail, the location changed, which caused normal mode to
be entered. Only when in hints mode we need to do that (issue #101).
Simon Lydell [Sat, 7 Sep 2013 18:32:31 +0000 (20:32 +0200)]
Fix: `Vim::enterNormalMode` should reset `@keys`
Otherwise keys accumulated in other modes might be interpreted when going
back to normal mode. For example, following a link with a hint ending with
"a" and then directly trying to follow another link, would do so in a new
tab. That last "a" was still in `@keys` when returning to normal mode, so
when trying to use the "f" command, it was interpreted as "af" instead.