docs: translate scroll wheel actions documentation to Chinese

[alaahong]

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

translate scroll wheel actions documentation to Chinese

Motivation and Context

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Translates scroll wheel actions documentation to Chinese

• Updates all section headings and body text to Chinese

• Maintains original document structure and code examples

• Improves formatting with better line breaks for readability

---

Diagram Walkthrough

flowchart LR
  A["English Documentation"] -- "translate content" --> B["Chinese Documentation"]
  B -- "preserve structure" --> C["Updated wheel.zh-cn.md"]

Loading

File Walkthrough

Relevant files

Documentation

wheel.zh-cn.md Complete Chinese translation of wheel documentation            website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md Translates page title from "Scroll wheel actions" to "滚轮操作" Translates all 6 section headings to Chinese Translates all descriptive text and explanations to Chinese Reformats text with improved line breaks for better readability Preserves all code examples and technical references unchanged +45/-44

---

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	4d78439
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/6a5bfa5fd66faf0008bf20ab
😎 Deploy Preview	https://deploy-preview-2551--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not Applicable: The PR only updates documentation text without adding code that performs critical actions or logging, so audit trail requirements are not applicable to the changed lines. Referred Code title: "滚轮操作" linkTitle: "滚轮" weight: 6 description: > 一种用于与网页交互的滚轮输入设备的示意. --- {{< badge-version version="4.2" >}} {{< badge-browser browser=Chromium wpt="perform_actions/wheel.py" >}} 在页面上滚动有 5 种情况. ## 滚动到元素 这是最常见的场景. 与传统的点击和发送按键的方法不同, 动作类不会自动将目标元素滚动到视图中, 因此如果元素不在视口内, 就需要使用此方法. 此方法仅将一个网页元素作为参数. ... (clipped 134 lines) Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Not Applicable: The changes are documentation-only and introduce no executable error handling paths; robustness criteria cannot be assessed from these content edits. Referred Code 在页面上滚动有 5 种情况. ## 滚动到元素 这是最常见的场景. 与传统的点击和发送按键的方法不同, 动作类不会自动将目标元素滚动到视图中, 因此如果元素不在视口内, 就需要使用此方法. 此方法仅将一个网页元素作为参数. 无论该元素是在当前视图屏幕的上方还是下方, 视口都会滚动, 使该元素的底部位于屏幕底部. {{< tabpane text=true >}} {{< tab header="Java" >}} {{< gh-codeblock path="/examples/java/src/test/java/dev/selenium/actions_api/WheelTest.java#L17-L20" >}} {{< /tab >}} {{< tab header="Python" >}} {{< gh-codeblock path="/examples/python/tests/actions_api/test_wheel.py#L11-L14" >}} ... (clipped 124 lines) Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct misleading section heading translation Correct a misleading section heading. The current translation incorrectly states scrolling is from an element's offset, while the section describes scrolling from the viewport's offset. The heading should be updated to reflect this. website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md [146] -## 从给定元素的原点偏移量处滚动指定的距离 +## 从视口内的一个偏移量开始，按给定距离滚动 Apply / Chat Suggestion importance[1-10]: 7 __ Why: This suggestion correctly identifies a significant inaccuracy in the documentation. The translated heading, following a misleading original English heading, contradicts the section's description. The proposed change corrects this, making the documentation accurate.	Medium
General	Improve heading translation for clarity Improve the Chinese translation of the heading "Scroll from an element by a given amount" for better clarity. The current translation can be misinterpreted; the proposed change clarifies that the element is the starting point for the scroll. website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md [75] -## 将元素按照给定的量进行滚动 +## 从一个元素位置开始，按给定距离滚动 Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion correctly identifies that the translated heading is slightly ambiguous and proposes a clearer version that better reflects the original English intent of scrolling from an element, not scrolling the element itself.	Low
Update

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 10 rules

1. Heading origin mismatch 🐞 Bug ≡ Correctness

Description

In the final scenario, the section heading says the scroll origin is an element, but the body text
(and the English source) describes scrolling from the viewport origin; this is contradictory and can
mislead readers about which API scenario is being documented.

Code

website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[R146-153]

+## 从给定元素的原点偏移量处滚动指定的距离

-The final scenario is used when you need to scroll only a portion of the screen,
-and it is already inside the viewport.
+最后一种情况适用于您需要滚动屏幕的某一部分, 
+而该部分已处于视口内的情况.

-This uses the "Scroll From" method again, but the viewport is designated instead
-of an element. An offset is specified from the upper left corner of the
-current viewport. After the origin point is determined,
-the page will be scrolled by the provided delta x and delta y values.
+这再次使用了“从...滚动”的方法, 但这次指定的是视口而非某个元素. 
+从当前视口的左上角开始指定偏移量. 
+确定原点后, 页面将根据提供的 x 偏移量和 y 偏移量进行滚动.

Evidence

The zh-cn heading explicitly references an element while the section body immediately states the
viewport is used instead; the English page confirms the viewport-origin description for this
scenario.

website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[146-153]
website_and_docs/content/documentation/webdriver/actions_api/wheel.en.md[144-152]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The final section heading claims the origin is an element (元素), but the section’s explanation says the origin is the viewport (视口). This mismatch is confusing and makes the translated section internally inconsistent.

### Issue Context
The English source for the same section describes using the viewport as the origin point.

### Fix Focus Areas
- website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[146-153]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Unintended hard line breaks 🐞 Bug ⚙ Maintainability

Description

Lines in the “从...滚动” section include double trailing spaces, which Markdown interprets as explicit
hard line breaks; this can create inconsistent rendering and is the kind of whitespace change called
out as risky in the repo’s PR review guidelines.

Code

website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[R79-82]

+要执行此操作, 请使用“从...滚动”方法, 
+该方法需要 3 个参数.  
+第一个参数表示起始点, 我们将其指定为元素,  
+后两个参数分别是 x 偏移量和 y 偏移量的值.

Evidence

The affected lines show extra trailing spaces at the end of lines, and the repo’s own review
guidelines warn that whitespace changes can break rendered docs.

website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[79-82]
.github/pr_review.md[7-9]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
A couple of lines end with two trailing spaces, which forces a hard line break in Markdown rendering. This can lead to unexpected formatting differences vs other pages that use semantic linefeeds without forced breaks.

### Issue Context
The repository review guidelines explicitly warn that small whitespace changes can break rendered documentation.

### Fix Focus Areas
- website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[79-82]
- .github/pr_review.md[7-9]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Heading origin mismatch 🐞 Bug ≡ Correctness

In the final scenario, the section heading says the scroll origin is an element, but the body text
(and the English source) describes scrolling from the viewport origin; this is contradictory and can
mislead readers about which API scenario is being documented.

Agent Prompt

### Issue description
The final section heading claims the origin is an element (元素), but the section’s explanation says the origin is the viewport (视口). This mismatch is confusing and makes the translated section internally inconsistent.

### Issue Context
The English source for the same section describes using the viewport as the origin point.

### Fix Focus Areas
- website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[146-153]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

2. Unintended hard line breaks 🐞 Bug ⚙ Maintainability

Lines in the “从...滚动” section include double trailing spaces, which Markdown interprets as explicit
hard line breaks; this can create inconsistent rendering and is the kind of whitespace change called
out as risky in the repo’s PR review guidelines.

Agent Prompt

### Issue description
A couple of lines end with two trailing spaces, which forces a hard line break in Markdown rendering. This can lead to unexpected formatting differences vs other pages that use semantic linefeeds without forced breaks.

### Issue Context
The repository review guidelines explicitly warn that small whitespace changes can break rendered documentation.

### Fix Focus Areas
- website_and_docs/content/documentation/webdriver/actions_api/wheel.zh-cn.md[79-82]
- .github/pr_review.md[7-9]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools