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.