vimium
vimium copied to clipboard
philc
Vimium Not Working with AWS Management Console
Steps:
Go to AWS Console and attempt to use Vimium.
Expected Results: At least to retain some keybindings (vomnibar)
Actual: Most of the time no keyboard shortcuts are registered (hints, vomnibar, reload) This is especially the case when launching EC2 instances.
I noticed Vimium acting up while in the EMR Console of AWS. Sometimes ? brings up Vimium's help window, sometimes it doesn't. I noticed x wasn't working to close the current tab, and then I checked ? and it didn't work either.
Is there anything we can do to help diagnose this? Any additional information we could provide?
When you said no shortcuts are registered, would those keys generate new characters in a remote terminal (in other words, were you in a mode of "typing some terminal commands"?
I was able to replicate the issue this morning as follows:
- login to AWS Management Console
- press
?and see that it brings up the Vimium help screen - go to EMR console and go to list of EMR on EC2 clusters
- press
?and see that it brings up the Vimium help screen - go to EC console and go to list of running instances
- press
?and see that it does not bring up the Vimium help screen
When you said
no shortcuts are registered, would those keys generate new characters in a remote terminal (in other words, were you in a mode of "typing some terminal commands"?
No, it is not in the Insert Mode. And I found when i am it the S3, Billing Management and so on, the vimium works, but in EC2 it does not work.
I've opened an AWS Support case to bring this to the attention of the AWS EC2 team.
Here is what AWS EC2 support said:
I understand you are experiencing difficulty using the Vimium plugin with Chrome when accessing the EC2 page in the AWS Console.
I personally tested this plugin in both Firefox and Chrome. I was unable to reproduce the issue you reported when using Firefox. However, when using Chrome I did notice some inconsistency with the Vimium plugin accepting keyboard input.
I saw that when the focus was in the main frame of the page, i.e. the top bar showing the search bar, current region, and current user, keyboard input was accepted by the Vimium plugin and all its functionality worked. When switching focus to the next frame showing Resources, Vimium would not recognize any keyboard input. I verified this using the logging output from Vimium itself.
Unfortunately it is not possible for us to guarantee compatibility with all 3rd party browser extensions. It may be necessary for you to communicate with the developer of this extension and request that they make the required changes to expand the compatibility to work with pages such as the EC2 page in the AWS Console. As this functionality works in Firefox, there appears to be some unique aspect of Chrome that affects Vimium's functionality.
I haven't looked into this, but it's pretty impressive that the AWS support person tried out Vimium to reproduce the issue!
On Tue, Jul 26, 2022 at 12:39 PM, Aleksey Tsalolikhin < @.*** > wrote:
Here is what AWS EC2 support said:
I understand you are experiencing difficulty using the Vimium plugin with Chrome when accessing the EC2 page in the AWS Console.
I personally tested this plugin in both Firefox and Chrome. I was unable to reproduce the issue you reported when using Firefox. However, when using Chrome I did notice some inconsistency with the Vimium plugin accepting keyboard input.
I saw that when the focus was in the main frame of the page, i.e. the top bar showing the search bar, current region, and current user, keyboard input was accepted by the Vimium plugin and all its functionality worked. When switching focus to the next frame showing Resources, Vimium would not recognize any keyboard input. I verified this using the logging output from Vimium itself.
Unfortunately it is not possible for us to guarantee compatibility with all 3rd party browser extensions. It may be necessary for you to communicate with the developer of this extension and request that they make the required changes to expand the compatibility to work with pages such as the EC2 page in the AWS Console. As this functionality works in Firefox, there appears to be some unique aspect of Chrome that affects Vimium's functionality.
— Reply to this email directly, view it on GitHub ( https://github.com/philc/vimium/issues/3605#issuecomment-1195901453 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAACDFWAVRXYE5TMWCD7QCLVWA5FZANCNFSM4OF4OECQ ). You are receiving this because you are subscribed to this thread. Message ID: <philc/vimium/issues/3605/1195901453 @ github. com>
Thank you atsalolikhin-spokeo.
Is there any way to use AWS without a America bank account? I mean my card from a bank in China was refused by AWS, so I still can not test it by myself.
Below is a screenshot of this issue replicated in the new EC2 console of AWS.
If you see below the "outer frame" gets assigned the shortcut keys but not the "inner frame"
Screenshot
Any progress here? Is there any possibility to get vimium working in AWS console?
@gdh1995 "AWS sign-up requires that you have a valid credit card on file." https://aws.amazon.com/blogs/aws-cloud-financial-management/a-quick-overview-of-aws-payment-methods/
I mean my card from a bank in China was refused by AWS, so I still can not test it by myself.
Just curious, does your card have either a VISA or MasterCard logo?
No it doesn't. I live in China (mainland) and then my usual cards only support "UnionPay".
@gdh1995 https://repost.aws/knowledge-center/accepted-payment-methods says that AWS accepts China UnionPay (CUP) credit card but also notes that "To create an AWS account, you must use a CUP credit card that supports USD currency."
Does your CUP credit card support USD currency?
Um not. But a CUP with USD is much easier than Visa, so let me borrow one when I'm rest enough in this year...