Skip to content

Move away from using chrome commands #9

@RealP

Description

@RealP

Issue

Currently we use chrome commands to capture keyboard events and inject actions in the background script. This has the limitation of not allowing more the 4 keyboard shortcuts to be set by default.

While we can add as many shortcuts as we want using this method, the fact that some are not set by default is confusing.

Possible Solutions

  1. Event listeners could be adding in the contentScript.js. Similar to how Alt+Click works today.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions