code-charity / code-charity/youtube

Allow Keybind Exclusivity in Task Assignment

Open
#2,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request good first issue help wanted up-for-grabs
Dominant language
JavaScript
Stars
4.6k
Forks
996
Avg merge
2d 15h
Merged PRs (30d)
7

Description

⚬ PROBLEM:
The YouTube extension currently allows users to assign the same keybind to multiple tasks simultaneously, which can potentially lead to conflicts and confusion among users.

⚬ SOLUTION:
Introduce a feature that enables keybind exclusivity when assigning tasks. When a user selects a keybind for a particular task, the extension should prompt a dialog for confirmation before removing that keybind from any other tasks to prevent conflicts.

⚬ ALTERNATIVES:
I thought in two options:

  • A dialog prompt for confirmation before removing the keybind from other tasks.
  • Automatic removal of the keybind from other tasks without a confirmation dialog.

⚬ RELEVANCE / SCOPE:
This feature enhancement would benefit all users who utilize shortcuts, as it enhances clarity and reduces potential conflicts in task assignment.

⚬ SIDE EFFECTS:
I don't think that implementing this feature introduce conflicts or adverse effects.

⚬ CONTEXT:
This behavior aligns with common practices observed in many sites and applications, where the same keybind is typically not allowed to be assigned to multiple functions simultaneously.

SHORT Table (Summary)
Problem Assigning the same keybind to multiple tasks simultaneously
Solution Implement keybind exclusivity to prevent conflicts
Alternatives Offer a dialog prompt for confirmation or automatic removal
Scope Users who utilize shortcuts
Side effects Not expected to introduce conflicts or adverse effects
Context Common practice in many sites and applications

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

The issue names no files, tests, or entry points. Start by locating the keybind assignment flow and its task-selection UI, then resolve whether confirmation is required before removing duplicate bindings; done means a selected keybind cannot remain assigned to multiple tasks and the chosen behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.