Skip to content
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

mat-select should have a "selectionMade" output #17534

Open
marcoliceti opened this issue Oct 29, 2019 · 2 comments
Open

mat-select should have a "selectionMade" output #17534

marcoliceti opened this issue Oct 29, 2019 · 2 comments
Labels
area: material/select feature This issue represents a new feature or feature request rather than a bug or bug fix P4 A relatively minor issue that is not relevant to core functions

Comments

@marcoliceti
Copy link

Feature Description

mat-select has an output that can be used to be notified when selection changes. This is not useful when you need to be notified also when the current selection is confirmed, i.e.

  1. Current selected option is "foo".
  2. User clicks on the select control and clicks again on "foo".

Use Case

I don't see why this event shouldn't be notified. Any user selection can be meaningful, not only when the selected option changes.

A concrete use case is when you are implementing a "smart" control that switches from a simple label to an actual select when you click on it and then switches back to a simple label when a selection is made (possibly confirming the currently selected option).

Without the requested feature, the mat-select element will remain visible each time the user confirms the currently selected option, thus breaking the kind of UX that I described.

@marcoliceti marcoliceti added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Oct 29, 2019
@mmalerba mmalerba added the needs triage This issue needs to be triaged by the team label May 20, 2020
@annieyw annieyw added area: material/select P4 A relatively minor issue that is not relevant to core functions and removed needs triage This issue needs to be triaged by the team labels May 26, 2020
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 22, 2022

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.

@angular-robot
Copy link
Contributor

angular-robot bot commented Mar 14, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: material/select feature This issue represents a new feature or feature request rather than a bug or bug fix P4 A relatively minor issue that is not relevant to core functions
Projects
None yet
Development

No branches or pull requests

4 participants