facebook/lexical

better support for keyboard accessibility

Open

#6,006 建立於 2024年5月2日

在 GitHub 查看
 (6 留言) (0 反應) (0 負責人)JavaScript (16,523 star) (1,349 fork)batch import
contribution-weekenhancementgood first issue

描述

In general using "Enter" on a toolbar that makes changes to lexical is problematic.

Lets say I have a button that toggles "bold" and it's triggered using the "Enter" key on the mouse-down event which calls dispatchCommand(FORMAT_TEXT_COMMAND...) - this causes lexical to get focus and then handle the Enter key which can replace the selected text with a new line.

adding the e.preventDefault to the event solves this problem but the focus still moves from the toolbar to the editor.

I'm not sure how to handle this...

貢獻者指南

技術棧
javascript
領域
accessibilityfrontend
議題類型
accessibility
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
JavaScriptevent handlingaccessibility principles
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate focus management in Lexical's toolbar components. Examine the use of dispatchCommand and how Enter key events propagate. Consider implementing a pattern that prevents default on toolbar buttons to avoid unwanted editor interaction while maintaining keyboard accessibility. Look at existing accessibility documentation or issues for similar patterns. Review comments on issue #6006 for community suggestions.
better support for keyboard accessibility · facebook/lexical#6006 | Good First Issue