fix(grid): fix resize bar cover by header

[gimmyhehe]

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

• Style
  • Improved the visibility of the column resize bar in tables by increasing its stacking order, ensuring it appears above more elements during column resizing.

[coderabbitai]

Walkthrough

The z-index value for the resizable bar in the table grid styles was increased from 4 to 21 in two LESS files. This adjustment ensures the resizable bar appears above more elements in the stacking context. No other style properties or selectors were changed.

Changes

Files	Change Summary
packages/theme-saas/src/grid/table.less, packages/theme/src/grid/table.less	Increased z-index of the table grid resizable bar from 4 to 21

Poem

A rabbit hops where tables grow,
Resizable bars now steal the show.
With z-index high, they leap above,
Overlapping all with a gentle shove.
In the garden of grids, order is clear—
The resizable line now leads the cheer!
🥕✨

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

packages/theme-saas/src/grid/table.less (1)

709-711: Z-index is hard-coded; move to a design token to avoid future drift

The bar now sits on z-index: 21, which is just one step above the z-20 scrollbar wrapper defined ~L1000. This solves the header–overlay issue, but sprinkling magic numbers makes cross-theme consistency brittle.

Recommend introducing a shared variable, e.g.:

@grid-resize-bar-z: 21; // keep in variables.less

&__resizable-bar {
  ...
-  @apply ~'z-[21]';
+  @apply ~'z-[@{grid-resize-bar-z}]';
}

packages/theme/src/grid/table.less (1)

639-642: Duplicate hard-coded z-index – centralise with a variable

Same concern as the SaaS theme: z-index: 21 is repeated here. Consider reusing a single token (@grid-resize-bar-z) for both themes to keep them in lock-step and avoid future mismatches.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4cbe804 and 305d240.

📒 Files selected for processing (2)

• packages/theme-saas/src/grid/table.less (1 hunks)
• packages/theme/src/grid/table.less (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*`: 用于写产品需求和开发文档的文件，需求应尽量写得简单清晰易懂。 在需求设计阶段应遵从逐步迭代的原则，早期版本可以尽量简洁。

**/*: 用于写产品需求和开发文档的文件，需求应尽量写得简单清晰易懂。
在需求设计阶段应遵从逐步迭代的原则，早期版本可以尽量简洁。

📄 Source: CodeRabbit Inference Engine (.cursor/rules/product.mdc)

List of files the instruction was applied to:

• packages/theme/src/grid/table.less
• packages/theme-saas/src/grid/table.less

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

• GitHub Check: PR Unit Test
• GitHub Check: PR E2E Test (pnpm test:e2e3)