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

描述

此议题没有描述。

贡献者指南

技术栈

typescriptreact

领域

frontend

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

half day

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

mostly clear

前置要求

Basic knowledge of ReactFamiliarity with Blueprint's Hotkey API

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

65

研究方向

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.