You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a duplicate of #4337, but it's not clear.
Describe the bug
I have this custom search engine...
g: http://www.google.com/search?q=%s Google
and this key binding...
map sg Vomnibar.activate keyword=g
... which should open the Vomnibar with the Google custom search engine already activated.
As of the latest update (2.0.3) this no longer works. Basically, the leading g to enable the search engine seems to be dropped.
Note... the search engine does still work if activated manually. So the issue seems to be to do with the Vomnibar activation, not the custom search engine itself.
To Reproduce
Steps to reproduce the behavior:
Add the custom search engine and key mapping above and type sg. We should be dropped into the custom Google search, but you're instead dropped into the generic Vomnibar.
Browser and Vimium version
Chrome: 117.0.5938.157
Vimium: 2.0.3
Thanks for your help.
The text was updated successfully, but these errors were encountered:
This might be a duplicate of #4337, but it's not clear.
Describe the bug
I have this custom search engine...
and this key binding...
... which should open the Vomnibar with the Google custom search engine already activated.
As of the latest update (2.0.3) this no longer works. Basically, the leading
g
to enable the search engine seems to be dropped.Note... the search engine does still work if activated manually. So the issue seems to be to do with the Vomnibar activation, not the custom search engine itself.
To Reproduce
Steps to reproduce the behavior:
Add the custom search engine and key mapping above and type
sg
. We should be dropped into the custom Google search, but you're instead dropped into the generic Vomnibar.Browser and Vimium version
Chrome: 117.0.5938.157
Vimium: 2.0.3
Thanks for your help.
The text was updated successfully, but these errors were encountered: