Skip to content

fix: Fixed the issue that the asynchronous setting of enterKeyHint fails when textarea is in autoFocus #6917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ShaoXuChenTTT
Copy link

@ShaoXuChenTTT ShaoXuChenTTT commented Jul 18, 2025

fix: Fixed the issue that the asynchronous setting of enterKeyHint fails when textarea is in autoFocus

当TextArea设置autoFocus时,通过useLayoutEffect设置的enterKeyHint属性在当次不会生效,需要重新触发焦点才能生效;

和豆酱沟通后提交pr,增加默认enterKeyHint设置;

Summary by CodeRabbit

  • 新功能
    • 在文本区域组件中新增对 enterKeyHint 属性的支持,提升虚拟键盘上的回车键标签显示效果。

…ils when textarea is in autoFocus

当TextArea设置autoFocus时,通过useLayoutEffect设置的enterKeyHint属性在当次不会生效,需要重新触发焦点才能生效;

和豆酱沟通后提交pr,增加默认enterKeyHint设置;
Copy link

coderabbitai bot commented Jul 18, 2025

📝 Walkthrough

Walkthrough

本次更改在 TextArea 组件中为 <textarea> 元素添加了 enterKeyHint 属性。该属性通过组件的 props 传递,并直接传递给原生 textarea 元素,实现对虚拟键盘回车键标签的上下文适配。未修改其他逻辑或控制流。

Changes

文件路径 变更摘要
src/components/text-area/text-area.tsx 添加了 enterKeyHint 属性到 <textarea>,通过 props 传递。

Poem

兔子敲键盘,属性添新颜,
enterKeyHint 上阵,虚拟键盘变,
输入更贴心,体验更周全,
代码轻轻改,用户笑开颜。
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

github-actions bot commented Jul 18, 2025

Preview is ready

@dosubot dosubot bot added size:XS This PR changes 0-9 lines, ignoring generated files. bug labels Jul 18, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/components/text-area/text-area.tsx (1)

96-102: useInputHandleKeyDown 参数对象每次渲染都会重新创建
此处直接向自定义 Hook 传递字面量对象,会导致 Hook 内部依赖全部变化而无法利用 useMemo / useCallback 等缓存,影响性能。可提前用 useMemo 封装:

-const handleKeydown = useInputHandleKeyDown({
-  onEnterPress: props.onEnterPress,
-  onKeyDown: props.onKeyDown,
-  nativeInputRef: nativeTextAreaRef,
-  enterKeyHint: props.enterKeyHint,
-})
+const keydownConfig = React.useMemo(
+  () => ({
+    onEnterPress: props.onEnterPress,
+    onKeyDown: props.onKeyDown,
+    nativeInputRef: nativeTextAreaRef,
+    enterKeyHint: props.enterKeyHint,
+  }),
+  [props.onEnterPress, props.onKeyDown, props.enterKeyHint],
+)
+const handleKeydown = useInputHandleKeyDown(keydownConfig)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7e04e8 and 2a0b0bc.

📒 Files selected for processing (1)
  • src/components/text-area/text-area.tsx (1 hunks)
🔇 Additional comments (2)
src/components/text-area/text-area.tsx (2)

45-53: 属性类型定义完备,接口保持向后兼容 👍
新增的 enterKeyHint 枚举值覆盖了规范中所有合法取值,并且保持可选,现有调用方不会破坏。


196-205: 确认 enterKeyHint 最低支持版本
MDN 文档显示 enterkeyhint 属性在 Chrome/Edge/Chrome for Android ≥ 77、Firefox ≥ 94、Safari ≥ 13.1(iOS Safari ≥ 13.4)等主流浏览器中均已支持¹。

  • 若您项目最低支持环境均在这些版本及以上,可直接依赖 React 原生属性,无需额外同步;
  • 如需兼容更早版本(如某些旧 Android WebView < 77),建议在组件内部补充一次原生属性赋值。

需关注位置:

  • 文件:src/components/text-area/text-area.tsx
  • 渲染 <textarea>(约 196–205 行)
  • useIsomorphicLayoutEffect 同步阶段

示例改动:

   <textarea
     …
     onKeyDown={handleKeydown}
-    enterKeyHint={props.enterKeyHint}
+    enterKeyHint={props.enterKeyHint}  // React 会原样输出 unknown attribute,HTML 属性名不区分大小写
   />

   // 布局阶段补充原生属性,覆盖老旧环境兼容差异
   useIsomorphicLayoutEffect(() => {
-    if (props.enterKeyHint && nativeTextAreaRef.current) {
-      (nativeTextAreaRef.current as any).enterKeyHint = props.enterKeyHint
-    }
+    if (props.enterKeyHint && nativeTextAreaRef.current) {
+      (nativeTextAreaRef.current as any).enterKeyHint = props.enterKeyHint
+    }
   }, [props.enterKeyHint])

请根据您的浏览器矩阵确认是否需要保留并使用上述原生属性同步方案。

¹ 引自 MDN:https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/enterkeyhint

@afc163 afc163 enabled auto-merge (squash) July 20, 2025 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant