-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocomplete: https://material.angular.io/components/autocomplete/overview weird behavior with simple autocomplete #15177
Comments
For what it's worth, you can also reopen it by pressing the up or down arrow keys. |
Shame on me... Not sure if this ticket is still actual then. But just to clarify: Is it possible to review my option (declare the behavior of autocomplete when we click on while some option is selected) ? Or it's quite complicated and not an option here? |
It shouldn't be complicated and comparing the UX to the autocomplete on the Google Search, it also reopens when you click on it again. @jelbourn should we try to match the UX from Google Search? |
@crisbeto I don't quite follow- are the steps
|
Yes. our autocomplete won't reopen when you click on it while it still has focus since we depend on the |
That seems reasonable, though I don't think it's the highest priority change |
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes #15177.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Currently if the user clicks an autocomplete to open it, selects an option and then clicks again, the panel won't open, because we use `focus` and the input was focused already. These changes add an extra `click` listener so the panel can reopen. Fixes angular#15177.
What is the expected behavior?
Ideally you should be given a choice: what should be the behavior when you click on autocomplete. But current behavior at least looks pretty unfriendly to user (from my point of view).
What is the current behavior?
Currently you're only able to open autocomplete again if you eith focus any other control and then focus autocomplete again; or remove the character from the selected option
What are the steps to reproduce?
https://material.angular.io/components/autocomplete/overview
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I believe the latest version of Angular
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: