Skip to content

Conversation

@gimmyhehe
Copy link
Member

@gimmyhehe gimmyhehe commented Feb 26, 2025

PR

修复当浏览器缩放时,表格错误地展示了溢出提示。
问题根因:
image
当浏览器缩放的情况下,元素宽度可能会出现小数点的情况。导致计算时,出现误差,导致了错误的判断了溢出。
image
解决方案:
增加0.1像素的计算误差,在误差范围内,判断为不溢出。

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
    • Refined tooltip behavior to prevent unintended fallback text from appearing when no content is provided.
    • Enhanced tooltip overflow detection by incorporating a slight tolerance, ensuring more consistent display.

@github-actions github-actions bot added the bug Something isn't working label Feb 26, 2025
@coderabbitai
Copy link

coderabbitai bot commented Feb 26, 2025

Walkthrough

The changes modify how tooltip content is set and how overflow is calculated for grid cells. The fallback to cell.textContent.trim() has been removed, so empty cell.innerText now results in an empty tooltip. Additionally, the overflow check now includes a tolerance of 0.1 pixels, refining the condition that determines if content exceeds the cell’s available width.

Changes

File(s) Changes
packages/vue/src/grid/src/tooltip/src/methods.ts - Removed fallback to cell.textContent.trim() for determining tooltip content.
- Adjusted overflow condition to include a 0.1 pixel tolerance.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as Grid Cell
    participant T as Tooltip Method

    U->>C: Hover over cell
    C->>T: Invoke tooltip logic
    T->>T: Check cell.innerText for content
    T->>T: Evaluate overflow with (rangeWidth + padding) against cell width + 0.1px tolerance
    T-->>U: Display tooltip if overflow condition met
Loading

Possibly related PRs

Suggested reviewers

  • zzcr

Poem

In the field of code so bright,
I hop with joy at each insight.
No fallback needed, the path is clear,
With tiny tolerances, I cheer!
Codes and carrots, both align—
A rabbit’s rhyme in pure design!
🥕🐇

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/tooltip/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

CodeRabbit's docstrings feature is now available as part of our Pro Plan! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

✨ Finishing Touches
  • 📝 Generate Docstrings

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

@petercat-assistant
Copy link

Walkthrough

修复了当浏览器缩放时,表格错误地展示溢出提示的问题。通过在计算时增加0.1像素的误差来解决由于元素宽度出现小数点而导致的误差问题。

Changes

文件 概要
packages/vue/src/grid/src/tooltip/src/methods.ts 修正了溢出判断逻辑,增加了0.1像素的误差以应对浏览器缩放导致的宽度计算误差。

const tooltip = this.$refs.tooltip
const wrapperElem = cell
const content = cell.innerText.trim() || cell.textContent.trim()
const content = cell.innerText.trim()

Choose a reason for hiding this comment

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

Removing cell.textContent.trim() might cause issues if innerText is not supported or behaves differently across browsers. Ensure that innerText is consistently supported in the environments where this code will run.

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Walkthrough

Fixed an issue where the table incorrectly displays overflow prompts when the browser zooms. The error problem caused by the decimal point of the element width is solved by adding an error of 0.1 pixels during calculation.

Changes

Documents Summary
packages/vue/src/grid/src/tooltip/src/methods.ts Fixed overflow judgment logic and added an error of 0.1 pixel to deal with width calculation errors caused by browser scaling.

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)
packages/vue/src/grid/src/tooltip/src/methods.ts (1)

57-59: Good fix for the browser scaling issue.

The addition of a 0.1 pixel tolerance to account for browser scaling decimal inaccuracies is a sensible solution to prevent erroneous overflow tips. The comment clearly explains the rationale.

One suggestion: Consider if this tolerance value (0.1) should be configurable or derived from some calculation rather than being a hardcoded constant, especially if different scaling scenarios might require different tolerance values.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e48a0d3 and ad7623c.

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

50-50: Consider potential impact of removing the textContent fallback.

The code has removed what appears to be a fallback to cell.textContent.trim() when cell.innerText is empty. This could affect tooltip behavior in cases where innerText is empty but textContent contains meaningful content.

Was this change intentional? If so, please ensure that removing this fallback doesn't prevent tooltips from appearing in legitimate cases.

@zzcr zzcr merged commit 02e08e9 into dev Feb 27, 2025
10 of 11 checks passed
@kagol kagol deleted the cgm/grid-show-overflow-tip branch April 14, 2025 12:26
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.

4 participants