HUD and text inputs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
(I cannot tell if the behaviour is wanted (-> Feature Request) or not (-> Bug))
Especially when you open a website that steals focus (and you do not want do deny this in general), maybe a website that you did not know yet, you may encounter the following problem: Vimium does not give you any information via the HUD whether the next press of f for example will a) input this character somewhere or b) do the usual link stuff.
Suggestion: Include the "entering characters" mode in the HUD
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
Start by locating the HUD rendering and the focus or text-input handling that determines whether keys are sent to an input or interpreted as Vimium commands. Trace how the HUD displays current modes, then inspect any related tests. Done means the HUD clearly indicates when character input mode is active, without changing the existing focus behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100