[autocomplete] Inconsistent behavior between single and multiple rendered values
Steps to reproduce
Steps:
- Open this link to live example: Single Value Rendering
- Compare behavior for the following between single value and multiple value rendering.
- Generally multiple value rendering behaves as I'd expect except where noted below.
ArrowLeft
Single value
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- Press left and observe that the set value is selected.
With no input present the set value is selected.
Multiple value
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- Press left and observe that no set value is selected.
- No matter where the cursor is no value is every selected when pressing ArrowLeft.
With no input present the most recent picked value is selected.
For either multiple or single I would think that a value could be selected if the cursor is at the beginning of the input, but at least it should have consistent behavior between the two.
Delete
Single value
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- Press delete and observe that the set value is deleted and that the deletion is sent to the input field as well deleting input text depending on where the cursor is.
Multiple values
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- Press delete and observe that no set value is removed and that only text is removed. To delete a set value it must first be selected. This is regardless of whether input is present or not.
Backspace
Single value
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- Press backspace and the set value is removed and the backspace is sent to the input field as well.
Multiple value
- Set a value and type some input.
- Place your cursor anywhere in the input field.
- No value is removed and backspace only ever affects text input unless all input is removed. If a value is selected and backspace is pressed it will remove that selected value.
Search keywords: autocomplete freesolo multiple single rendered values Backspace Delete ArrowLeft
No value is removed and backspace only ever affects text input
Under "Backspace/Multiple value/3." – backspace removes chips from a multiple autocomplete e.g. in this demo
No value is removed and backspace only ever affects text input
Under "Backspace/Multiple value/3." – backspace removes chips from a multiple autocomplete e.g. in this demo
Thanks for catching that, I've updated that point.
@ZeeshanTamboli @wjwat @aarongarciah
Hi! We are a team of 3 CMU students and would like to work on this issue as part of our Software Engineering course project. Could you confirm this is available to work on, and if so assign the issue to me? Thanks!
@harsher216 You are welcome to open PRs directly, be sure to link to this issue
I would also suggest you first verify each dot point in the issue description as I haven't gone through all of them myself, and break this up into multiple PRs whenever possible
@wjwat For "ArrowLeft", would you mind sharing a screen recording that shows the differences you describe? I'm not sure I fully understand the issue
In the multiple demos in the docs, when the input has focus with the caret at the end, and when there are values already selected, ArrowLeft clearly moves the focus from the textbox to the chips