fix: Use pointerDown to check if click with portal

[zombieJ]

ref #434

Summary by CodeRabbit

• 新功能

  • 更新了弹出窗口组件的事件处理，改用 onPointerDownCapture，提高了用户交互体验。
  • 增强了对指针事件的处理，防止弹出窗口在点击时意外关闭。

• 测试

  • 更新了测试用例，改用 fireEvent.pointerDown 和 fireEvent.mouseDown，提高事件模拟的准确性。
  • 扩展了对多个触发器的上下文菜单操作的测试，确保弹出窗口的可见性正确管理。

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

此次更改涉及多个文件，主要修改了与指针事件相关的功能。PopupProps接口中的事件处理器从onMouseDownCapture更改为onPointerDownCapture，以支持更好的指针事件捕获。useWinClick钩子引入了新的逻辑，以防止在弹出窗口内的点击事件意外触发关闭。TriggerProps接口和generateTrigger函数也进行了更新，以改善弹出窗口的可见性管理和响应性。最后，测试用例进行了调整，以更准确地模拟事件并验证组件行为。

Changes

文件路径	更改摘要
src/Popup/index.tsx	将PopupProps接口中的onMouseDownCapture更改为onPointerDownCapture。
src/hooks/useWinClick.ts	添加popupPointerDownRef以跟踪指针事件，更新onTriggerClose函数以防止意外关闭弹出窗口。
src/index.tsx	移除TriggerProps接口中的getDocument属性，更新generateTrigger函数以改善弹出窗口的事件处理和可见性管理。
tests/basic.test.jsx	将fireEvent.click替换为fireEvent.pointerDown和fireEvent.mouseDown，增强事件模拟的准确性。

Possibly related PRs

• fix: click on shadowDOM popup should not close it #480: 此PR处理弹出窗口与影子DOM交互的行为，与主PR中关于指针事件的事件处理修改相关。
• Revert "fix: click on shadowDOM popup should not close it" #485: 此PR试图撤销#480中的更改，表明对影子DOM弹出窗口点击事件处理的持续讨论，与主PR中的事件处理更改相关。
• fix: try to fix createPortal close case #492: 此PR专注于修复使用createPortal时弹出窗口的关闭行为，与主PR中事件处理和用户交互的更改相关。

Poem

在草地上跳跃的小兔，
指针事件来临，真是好事！
弹出窗口不再轻易关，
点击间欢笑声连连。
让我们一起庆祝这变化，
兔子们的乐园更加美妙！ 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.75%. Comparing base (d8bfea2) to head (1019cc9).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #493      +/-   ##
==========================================
+ Coverage   97.73%   97.75%   +0.01%     
==========================================
  Files          13       13              
  Lines         794      800       +6     
  Branches      239      239              
==========================================
+ Hits          776      782       +6     
  Misses         18       18              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.