Skip to content

Feature request. More granular Extension's hotkeys scope #683

@InsaneDoggo

Description

@InsaneDoggo

Would be nice to be able to limit hotkey' scope (i.e. where it can be triggered).

Example: (chrome-related terminology) I'm using "chrome.commands" API to control embedded player via "content scripts", to seek forward/backward by Ctrl + Left/Right arrow keys to be precise. This extension is supposed to work on specific URL. Arrows is very convenient and intuitive keys for mentioned player's actions so I don't want to use some weird/complex shortcut combos, at the same time I don't want those hotkeys to override my usual "browser experience" on other tabs/URLs e.g. while typing in search bar etc.

Possible solutions:

  1. Config in Manifest to limit scope to "active tab" + [optional] match specific URLs e.g. https://foo.bar/
  2. Provide API to invoke default implementation. e.g. as an extra callable parameter in "chrome.commands.onCommand.addListener".

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementEnhancement or change to an existing featureneeds-triage: firefoxFirefox needs to assess this issue for the first timeneutral: safariNot opposed or supportive from Safaritopic: commands

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions