Unclear from UI how "keys to exclude" should be separated (if at all)
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
In the extension settings, under "Excluded URLs and keys" / "Keys to exclude", it is not clear whether the "keys to exclude" should be separated by commas, whitespace, something else, or nothing at all.
Apparently, the answer is "nothing at all", but that's fairly unusual for a UI.
To Reproduce
View the extension options.
Browser and Vimium version
- Browser: Vivaldi 7.0.3495.6 stable (64-bit)
- OS: Linux
- Vimium version: 2.1.2
Comments
It would be helpful if the UI said exactly what separators are permitted (e.g. "the keys may, optionally, be separated by whitespace") as well as what's normally expected (e.g. "the keys should be a single string - e.g. fgh").
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 in the extension options UI and inspect the "Excluded URLs and keys" / "Keys to exclude" setting. Reproduce the ambiguity described in the issue, then identify the setting's label or help text and clarify the accepted separators and expected single-string format. Verify the wording in the options page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100