Feature Request: Option to enable on Restricted/Protected pages (with browser flag set)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Darkreader is able to do it, can Vimium do it too?
https://github.com/search?q=repo%3Adarkreader%2Fdarkreader+ProtectedPages&type=code
I'm poking around the codebase there to try to figure out how they pull it off. If I can figure it out I'll submit a PR, but I figured I'd open this now in case someone who's more skilled than me wants to take a crack at it.
Considering that for this option to work, the corresponding flag must be explicitly set in chrome://flags or about:config per-user, it seems like it's inherently non-risky (for Vimium) to provide this option for people who want to enable it.
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
The issue names no Vimium files or tests. Start by inspecting the JavaScript extension code and the referenced Dark Reader ProtectedPages implementation, then confirm how the required Chrome or Firefox browser flags affect restricted pages. Done means an explicitly opt-in setting enables Vimium on those pages without changing the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100