VisActor / VisActor/VTable

[Bug] 配置了首列,最后一列,最后一行不可框选中,但是选中中间部分后,往下滚动到最底部时会全部选中且包含了 首列 最后一列,最后一行,期望不选中

Open
#4,640 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
3.7k
Forks
486
Avg merge
1d 19h
Merged PRs (30d)
16

Description

Version

1.22.0

Link to Minimal Reproduction

Steps to Reproduce

select: {
highlightMode: 'cell',
blankAreaClickDeselect: true,
outsideClickDeselect: true,
headerSelectMode: 'inline',
cornerHeaderSelectMode: 'cell',
disableSelect: (col, row, table) => {
return col === 0 || row === table.records.length || col === table.columns.length
}
},

Current Behavior

主要是这么配置的
disableSelect: (col, row, table) => {
return col === 0 || row === table.records.length || col === table.columns.length
}

Expected Behavior

主要是这么配置的
disableSelect: (col, row, table) => {
return col === 0 || row === table.records.length || col === table.columns.length
}

Environment
- OS:
- Browser:
- Framework:
Any additional comments?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the reported selection settings, especially highlightMode "cell" and the disableSelect callback. Check how selection behaves after scrolling from middle rows to the bottom, including the first column, last column, and last row. Done means disabled boundary cells remain unselected after scrolling.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.