-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Description
Hi there, I got an annoying issue when using this fancy plugin. After searched the whole internet, finally I realized that this issue was caused by vimium.
And here, I would like to re-explain the previous issue again: #2768 , with more details.
OS: OS X 10.12
Chrome: Latest and most recent versions
IME: System built-in Chinese Pinyin (Simplified)
Details:
When we need to input some Chinese or Japanese words in form, we need to use corresponding IME, like Chinese Pingyin Input Method.
Usually, when we type a whole Chinese sentence, we key in many alphabet words, then they are converted to Chinese and show in the on-the-fly area of IME, then, after we press blank space, the Chinese chars will be sent to input box.
Easy and simple, aha? Key in alphabet words, IME convert them to Chinese chars, press blankspace, IME send the buffered Chinese to input box. just as follow:
(Please note that before Chinese were sent to inputbox, I pressed blank space)
If we want to give up(discard) the current buffered text(usually them are long), we just need to press ESC instead of blankspace, as follow:
Did you see that? when I want to discard whole buffered words, I just need to press ESC.
This is the good and normal behavior by default.
BUT, when I have vimium installed in Chrome, if I discard the buffered words by pressing ESC, the following annoying thing happened:
Did you see that? when I press ESC to discard the buffered text, the original alphabet was left over in the inputbox, which should be cleared or discarded. This is super annoying and frustrating when composing an email or something else, coz we need to use mouse to select those leftovers then delete, or delete them one by one.
I hope I described the problem clearly, it took me 50 minutes to make GIFs and reproduce this issue. but since I'm a 6+ years vimium user, I don't think 50m is a waste of time.
More than that, then I writing this issue, I found another forked plugin which resolved this bug perfectly:
https://chrome.google.com/webstore/detail/vimium%2B%2B/hfjbmagddngcpeloejdejnfgbamkjaeg
Here is the screenshot when using vimium++:
But again, I'm still a vimium user and want to make it better, hope this helps.
Please take a look at this issue, thank you guys so much.