When hotkeys conflict, trigger the callback from the most-local context only

Description

This issue does not include a description.

Contributor guide

Tech stack

typescriptreact

Domain

frontend

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Basic knowledge of ReactFamiliarity with Blueprint's Hotkey API

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65

Research direction

The issue is about resolving hotkey conflicts so that only the most local context's callback fires. Start by examining the Hotkey component and its context mechanism in the Blueprint source, likely under packages/core/src/components/hotkeys/. Look for how hotkeys are registered and how conflicts are currently handled. The desired behavior is to propagate the event to the nearest ancestor context and stop propagation. Review any existing tests or discussions in the repository. A solution could involve checking the event propagation and ensuring that only the closest matching hotkey triggers.