philc / philc/vimium

[Feature Request] Use native messaging to enable vimium on new tab and chrome store

Open
#4,256 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
27k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

Use native messaging to enable vimium on new tab and chrome store.
https://developer.chrome.com/docs/extensions/mv3/nativeMessaging/

Some extensions that use this method are autocontrol and external application launcher.

It would be great if vimium could use this as well.
Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Chrome native messaging documentation and examining how the referenced Autocontrol and External Application Launcher extensions use it. Determine the Vimium entry points involved in enabling the extension on new tabs and in the Chrome Web Store; done means a defined native-messaging approach that supports both requested contexts.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.