fix(Popup): popup demos 调优

[xiaoyatong]

🤔 这个变动的性质是？

• 新特性提交
• 日常 bug 修复
• 站点、文档改进
• 演示代码改进
• 组件样式/交互改进
• TypeScript 定义更新
• 包体积优化
• 性能优化
• 功能增强
• 国际化改进
• 重构
• 代码风格优化
• 测试用例
• 分支合并
• 其他改动（是关于什么的改动？）

🔗 相关 Issue

💡 需求背景和解决方案

☑️ 请求合并前的自查清单

⚠️ 请自检并全部勾选全部选项。⚠️

• 文档已补充或无须补充
• 代码演示已提供或无须提供
• TypeScript 定义已补充或无须补充
• fork仓库代码是否为最新避免文件冲突
• Files changed 没有 package.json lock 等无关文件

Summary by CodeRabbit

• 新功能
  • 提升了弹窗组件的交互体验：现在提供了两种不同的关闭方式，让用户操作更明确。
  • 优化了界面展示：更新了提示文本及弹窗的视觉布局，统一了图标尺寸和窗口位置，使整体设计更清晰易用。

[coderabbitai]

Walkthrough

此次 PR 对两个 Demo4 组件文件进行了调整，主要修改了 Popup 和 Cell 组件的属性配置及显示行为。更新包括修改标题文本、添加 closeable 与 closeIcon 属性、调整样式为 height: '40%'、设置 position 为 bottom、在 onClose 事件中增加日志打印，以及在 taro 版本中对关闭标签进行自闭合处理。同时，为第二个组件明确添加了 closeOnOverlayClick: false 属性。

Changes

文件	变更摘要
src/packages/popup/demos/h5/demo4.tsx src/.../taro/demo4.tsx	- 更新第一个 Cell 标题为 “阻塞点击 Overlay 关闭，方式1” - 对关联 Popup（showOverlayStop）增加 closeable 与 closeIcon 属性（H5 为数值设置；Taro 使用 <Failure size={12} />） - 样式更新为 height: '40%'，并设置 position 为 bottom - 在 onClose 事件中增加日志打印 - Taro 版本将 Popup 关闭标签改为自闭合形式 - 更新第二个 Cell 标题为 “阻塞点击 Overlay 关闭，方式2”，并为 Popup（showCloseIconStop）明确添加 closeOnOverlayClick: false

Sequence Diagram(s)

sequenceDiagram
    participant 用户 as 用户
    participant Popup as Popup 组件
    participant 日志 as Console
    用户->>Popup: 点击关闭图标
    Popup->>日志: 触发 onClose 并打印日志

Loading

Possibly related PRs

• refactor: popup 优化代码 #2944: 修改 Popup 组件行为和属性，与本次调整存在代码层面的关联。
• feat: demos for popup & dialog #2574: 同样对 Popup 与 Cell 组件的属性及展示进行了调整，主题相似。
• feat(popup): lockscroll 增加可选值 strict, 用于支持 iOS12 #2629: 包含对 Popup 组件的样式、位置和日志打印等方面的修改。

Suggested reviewers

• oasis-cloud

Poem

我是一只欢快的小兔，
在代码林中跳跃不停，
Popup 变得更灵动，
日志轻吟诉说新声，
每行代码皆似月光闪烁，
祝愿此改进带来无限惊喜！

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

 ERR_PNPM_OPTIONAL_DEPS_REQUIRE_PROD_DEPS  Optional dependencies cannot be installed without production dependencies

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fc2e7a5 and 8721dd7.

📒 Files selected for processing (2)

• src/packages/popup/demos/h5/demo4.tsx (1 hunks)
• src/packages/popup/demos/taro/demo4.tsx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test

🔇 Additional comments (13)

src/packages/popup/demos/taro/demo4.tsx (6)

12-12: 标题更新提升了Demo的清晰度

更改后的标题"阻塞点击 Overlay 关闭，方式1"更加明确地表示这是演示阻止覆盖层关闭的第一种方式，使Demo的目的更加清晰。

---

18-19: 增加了关闭按钮功能

添加了closeable和closeIcon属性，使弹出层增加了关闭按钮，提升了用户体验。使用Failure图标作为关闭按钮，样式设置恰当。

---

21-22: 改进了弹出层样式和位置

将样式从内边距调整为高度百分比设置，并明确指定了位置为底部，使弹出效果更加符合移动端交互习惯。

---

24-24: 增加了关闭事件日志

添加了控制台日志输出，有助于调试和演示onClose事件的触发时机，对开发者使用组件时理解事件流程很有帮助。

---

33-33: 标题更新使Demo更有条理

将第二个Cell的标题改为"阻塞点击 Overlay 关闭，方式2"，与第一个Cell形成呼应，使整个Demo的结构更加清晰，便于理解不同实现方式的区别。

---

44-44: 显式设置覆盖层点击行为

添加了closeOnOverlayClick={false}属性，明确指定点击覆盖层不会关闭弹出层，这是实现"方式2"的关键配置，使代码意图更加清晰。

src/packages/popup/demos/h5/demo4.tsx (7)

12-12: 标题更新提升了Demo的清晰度

更改后的标题"阻塞点击 Overlay 关闭，方式1"更加明确地表示这是演示阻止覆盖层关闭的第一种方式，使Demo的目的更加清晰。

---

18-19: 增加了关闭按钮功能

添加了closeable和closeIcon属性，使弹出层增加了关闭按钮，提升了用户体验。使用Failure图标作为关闭按钮，并设置了适当的尺寸。

---

21-22: 改进了弹出层样式和位置

将样式从内边距调整为高度百分比设置，并明确指定了位置为底部，使弹出效果更符合移动端交互习惯。这种配置更好地展示了组件的实际使用场景。

---

24-24: 增加了关闭事件日志

添加了控制台日志输出，有助于调试和演示onClose事件的触发时机，对开发者使用组件时理解事件流程很有帮助。

---

33-33: 标题更新使Demo更有条理

将第二个Cell的标题改为"阻塞点击 Overlay 关闭，方式2"，与第一个Cell形成呼应，使整个Demo的结构更加清晰，便于理解不同实现方式的区别。

---

40-40: 统一图标样式设置

更新了图标的宽高设置，使用了更明确的尺寸属性，保持了组件在整个Demo中的样式一致性。

---

44-44: 显式设置覆盖层点击行为

添加了closeOnOverlayClick={false}属性，明确指定点击覆盖层不会关闭弹出层，这使得第二种方式的实现逻辑更加清晰，也与标题描述保持一致。

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• 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 generate docstrings to generate docstrings 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.10%. Comparing base (fc2e7a5) to head (8721dd7).
Report is 2 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #3075   +/-   ##
==========================================
  Coverage      86.10%   86.10%           
==========================================
  Files            277      277           
  Lines          18408    18408           
  Branches        2807     2807           
==========================================
  Hits           15851    15851           
  Misses          2552     2552           
  Partials           5        5           

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

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.