Thank you for a very complete bug report! 👍 I only edited your hyperlink markup a bit.

Insert behavior on javascript heavy websites like Google Search can be challenging to understand, and I'm not sure if i should get you insert mode at all. In fact, i should only ignore one key, as described in the documentation (:h i):

If you only need to pass a single key to a JavaScript form field or another extension prefix the key with i. Also works to unshadow Iceweasel shortcuts like which are otherwise hidden in Vimperator.

Without being able to reproduce the old behavior myself, my guess would be that previously Google Search would eat any keys pressed after your first key ignore using i. This is no longer the case (and not necessarily a bad thing).

If all you want to do is to append to your search string, gi is the keystroke you want to use (:h gi):

Focus last used input field. If there is no last input field, it focuses the first input field. When used with [count] it directly jumps to the [count]th input field.

Does that solve your problem?

Also, there's #384

@timss , Thanks for the reply and the great suggestion.

nsert behavior on javascript heavy websites like Google Search can be challenging to understand, and I'm not sure if i should get you insert mode at all. In fact, i should only ignore one key, as described in the documentation (:h i):

I should say, I don't agree with that completely and more so, depends on the situation. While in the INSERT mode, Vimperator ignores all the commands and lets you type, and I believe this is why I used to get that behavior.
Previously, i was putting me in the IGNORE mode, and since typing anything in Google search page gets the focus of search-textbox instantly, Vimperator would switch to INSERT mode and off you go.

So something must have changed, either Firefox (like the bug you forwarded me in issue #384), Google's scripts or Vimperator. And no problem at all. I like your work around however there is little funny thing happening with it. g+i puts the cursor to the left far side of the text inside the search textbox which in my case isn't what I always want :) but for sure does the trick.

Thanks again for the solution recommended and keep to hear more about this 👍

I get what you're saying about ignore vs ignore all keys behaving differently. For now let's assume #384 is the root cause, and see where it gets us :-) This issue could possibly be closed as a duplicate in that case, if you're fine with that.

I like your work around however there is little funny thing happening with it. g+i puts the cursor to the left far side of the text inside the search textbox which in my case isn't what I always want :) but for sure does the trick.

As suggested in #192, you can add a mapping which puts you in the end of the input element regardless of your previous position:

noremap gi gi<End>

Thanks @timss. Will do.

Great. Thanks again for your reporting.

Closed as duplicate of #384