[Bug] 配置了首列,最后一列,最后一行不可框选中,但是选中中间部分后,往下滚动到最底部时会全部选中且包含了 首列 最后一列,最后一行,期望不选中
Nobody has claimed this yet.
- 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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