Vimium does not work on AWS Cloudwatch console
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When using the AWS cloudwatch console, vimium stops working as you navigate to the cloudwatch log groups section.
To Reproduce
Steps:
- Log into your AWS account
- navigate to Cloudwatch console.
- From the side bar click on Log Groups
- and vimium stops working altogether
Browser and Vimium version
Browser: Brave 1.80.125
Vimium Version: 2.3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by opening AWS CloudWatch, selecting Log Groups, and checking whether Vimium stops responding. The payload names no repository files or tests, so first locate the code handling pages or frames on the CloudWatch console. Done means Vimium remains usable after navigating to Log Groups and the behavior is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100