[Bug] Inconsistent selection behavior
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 486
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 16
Description
Version
1.20.3
Link to Minimal Reproduction
No
Steps to Reproduce
-
disableSelectOnContextMenu: true
Assuming you currently have a selected cell and right-click on it, the selection will not disappear -
disableHeaderSelect: true、disableSelect: true
Assuming a cell is selected and a certain range cannot be selected, clicking on that range will cause the previously selected cell to disappear;
Current Behavior
The selection effect of disabling Header Select and disabling Select should be consistent with disabling Select On Context Menu. Previously, there were selected cells, but clicking on 'Do Not Clear Selected Cells' should not clear them
Expected Behavior
When a column A has disabled HeaderSelect and disabled Selec properties set, first click on another column B cell to select it, and then right-click on column A cell to click, hoping that the previously selected cell still exists
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
Reproduce the behavior in VTable 1.20.3 using disableSelectOnContextMenu, disableHeaderSelect, and disableSelect as described in the issue. Trace the table's selection handling from those settings and verify that clicking or right-clicking a disabled cell preserves the previously selected cell consistently.
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
- Mostly clear
- Newbie friendliness
- 42/100