Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Highlighting an input field automatically exits manually-entered insert mode #2373

Open
inkounter opened this issue Dec 15, 2016 · 2 comments

Comments

@inkounter
Copy link

inkounter commented Dec 15, 2016

Activating insert mode works as expected, but once I highlight a text input field, vimium puts me back in normal mode.

#2140 implies that under the hood, text input fields are actually handled as if the user is in input mode (which makes sense), but the user should probably stay in the previous mode (whether that's insert or normal) after deselecting the text input field.

It may be worth mentioning that I initially found this behavior while filling out an input form involving both text inputs and dropdown (HTML <select>) fields. With a dropdown field highlighted, vimium is presumably still in normal mode, so I can't, for example, type in "Ver" to search for "Vermont". Switching to insert mode before typing in the substring search does work, however. It's just that as soon as I tab to the next field, I'm forced back to normal mode, so if I tab back, I have to re-enter insert mode.

Arguably, these could be two separate issues:

1. Highlighting an input field forces the user to leave insert mode.
2. HTML <select> elements do not trigger vimium to enter insert mode.

Edit:
Google Chrome 54.0.2840.101 (Official Build) (64-bit)
Vimium v1.57

Edit 2:
The <select> fields work fine; I was just dealing with an exception on a specific site that had their own implementation of dropdowns.

@smblott-github
Copy link
Collaborator

What you describe is correct and indeed a little odd, @arnoldkao. It's a legacy of how insert mode was originally implemented, and the current implementation contains a hack to retain that legacy behaviour.

I'm not sure we should change it, though.

@devnoname120
Copy link

@smblott-github I also have this issue. This is particularly annoying when using Duolinguo because it supports keyboard navigation but I repeatedly need to enable input mode after every time I input some text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants