Bug reportOct 9, 2026· 0:18· 0 views
Mantine v9 MultiSelect: Backspace removes last value despite readOnly
0:18 total
Comments · 0
Be the first to comment.
Bug report— by SceneRecap AI
mediumMultiSelect
os: macOSlocale: en-USbrowser: Chromium 151.0.7922.34viewport: 1280x720
Repro steps
- 1.Open the Mantine MultiSelect component page with values selected in a readOnly input field.
- 2.Click into the MultiSelect search input field.
- 3.Press the Backspace key.
- 4.Press Backspace again in the search input.
Expected
A readOnly MultiSelect field should prevent modifying selected tags; pressing Backspace should not remove existing values.
Actual
Pressing Backspace deletes the preceding selected chip ('Angular' is removed at 9.0s, and 'React' is removed at 15.0s), clearing values from a readOnly field.
Evidence
visualAt 7.0s, both 'React' and 'Angular' are selected. After Backspace at 8.5s, frame at 9.0s shows 'Angular' removed.
visualAfter a second Backspace press at 13.2s, frame at 15.0s shows 'React' also removed, leaving the field empty.
Issue markdown (copy-paste ready)
### Summary
When a `MultiSelect` component is marked as `readOnly`, pressing `Backspace` inside the input field deletes selected value chips.
### Steps to Reproduce
1. Render or open a `MultiSelect` component with values ('React', 'Angular') and `readOnly` set.
2. Click inside the search input (timestamp 6.4s).
3. Press `Backspace` (timestamp 8.5s).
4. Press `Backspace` again (timestamp 13.2s).
### Expected Behavior
Values should remain locked; pressing `Backspace` should not remove selected items when the input is `readOnly`.
### Actual Behavior
- The first Backspace removes the 'Angular' tag (visible at 9.0s).
- The second Backspace removes the 'React' tag (visible at 15.0s).
*Recorded with SceneRecap.*Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →