Skip to content

fix: fix grid width error when grid has scrollbar#3421

Merged
zzcr merged 1 commit intodevfrom
cgm/fix-grid-scrollbar
May 14, 2025
Merged

fix: fix grid width error when grid has scrollbar#3421
zzcr merged 1 commit intodevfrom
cgm/fix-grid-scrollbar

Conversation

@gimmyhehe
Copy link
Copy Markdown
Member

@gimmyhehe gimmyhehe commented May 13, 2025

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Bug Fixes
    • Improved table display to prevent unwanted scrollbars from appearing when zooming in the browser.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented May 13, 2025

Walkthrough

The update adjusts the calculation of the table body width within the autoCellWidth method to address scrollbar appearance issues during browser zoom. The method now uses clientWidth - 1 instead of flooring the bounding rectangle width, and the accompanying comment has been revised for clarity.

Changes

File(s) Change Summary
packages/vue/src/grid/src/table/src/methods.ts Modified table body width calculation in autoCellWidth to use clientWidth - 1 and updated comment.

Poem

🐇
A pixel here, a pixel gone,
Scrollbars vanish, zoom moves on.
No more math with floors and bounds,
Just client width—subtract a round!
Table neat and scrollbars few,
Cheers to code that fits the view.

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.

packages/vue/src/grid/src/table/src/methods.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

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

@github-actions github-actions bot added the bug Something isn't working label May 13, 2025
@petercat-assistant
Copy link
Copy Markdown

Walkthrough

This pull request addresses a grid width error that occurs when a grid has a scrollbar. The change modifies the calculation of the grid's width to prevent the appearance of a scrollbar during browser zoom by adjusting the width calculation to account for fractional pixel values.

Changes

File Summary
packages/vue/src/grid/src/table/src/methods.ts Adjusted the calculation of bodyW to use clientWidth - 1 to handle fractional pixel widths and prevent scrollbar appearance during zoom.

let overflowY = bodyEl.scrollHeight > bodyEl.clientHeight
// 解决缩放时会出现滚动条的问题
let bodyW = Math.floor(bodyEl.getBoundingClientRect().width)
// 当浏览器缩放时,实际宽度会出现小数点,clientWidth会取整,此处减去1px解决缩放时会出现滚动条的问题
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The adjustment of bodyW to bodyEl.clientWidth - 1 is a critical fix to handle fractional pixel widths that can cause scrollbars to appear during browser zoom. This change ensures that the grid width calculation is more accurate and prevents unwanted scrollbars.

Copy link
Copy Markdown

@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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d04efe4 and 046a2d2.

📒 Files selected for processing (1)
  • packages/vue/src/grid/src/table/src/methods.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)

Comment on lines +1019 to +1020
// 当浏览器缩放时,实际宽度会出现小数点,clientWidth会取整,此处减去1px解决缩放时会出现滚动条的问题
let bodyW = bodyEl.clientWidth - 1
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

Avoid subtracting a hardcoded pixel; use Math.floor on getBoundingClientRect().width
Subtracting 1 px unconditionally can undercut the true available width (even when there’s no fractional pixel) and skew the computed scrollbarWidth by +1, potentially misaligning sticky columns. Instead, floor the fractional width from the bounding rect to handle sub-pixel values without a hardcoded hack.

-    // 当浏览器缩放时,实际宽度会出现小数点,clientWidth会取整,此处减去1px解决缩放时会出现滚动条的问题
-    let bodyW = bodyEl.clientWidth - 1
+    // 使用 getBoundingClientRect 的宽度取整,避免浏览器缩放带来的分数像素导致滚动条
+    const bRectWidth = bodyEl.getBoundingClientRect().width
+    let bodyW = Math.floor(bRectWidth)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
// 当浏览器缩放时,实际宽度会出现小数点,clientWidth会取整,此处减去1px解决缩放时会出现滚动条的问题
let bodyW = bodyEl.clientWidth - 1
// 使用 getBoundingClientRect 的宽度取整,避免浏览器缩放带来的分数像素导致滚动条
const bRectWidth = bodyEl.getBoundingClientRect().width
let bodyW = Math.floor(bRectWidth)

@zzcr zzcr merged commit 21a23b3 into dev May 14, 2025
10 of 11 checks passed
@zzcr zzcr deleted the cgm/fix-grid-scrollbar branch May 14, 2025 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants