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.