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

bug(mat-select): "mat-select-trigger" breaks the view with 'mat-chip-list' component #24796

Closed
1 task done
dmytrodemchenko opened this issue Apr 18, 2022 · 2 comments
Closed
1 task done
Labels
needs triage This issue needs to be triaged by the team

Comments

@dmytrodemchenko
Copy link

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

13.1.1

Description

With a new update, it started to break the view which is not expected for multiple selections.
Demo: https://stackblitz.com/edit/angular

Screenshot 2022-04-18 at 16 06 23

Reproduction

Provided a demo in description in StackBlitz

Expected Behavior

Should work as it was previously in 13.1.1 or somehow handle it )

Actual Behavior

Broken view of the mat-select component.

Environment

  • Angular:
  • CDK/Material:
  • Browser(s):
  • Operating System (e.g. Windows, macOS, Ubuntu):
@dmytrodemchenko dmytrodemchenko added the needs triage This issue needs to be triaged by the team label Apr 18, 2022
@crisbeto
Copy link
Member

Chips inside of a select are not an interaction pattern we support, because it doesn't make sense in terms of accessibility. It happened to work in the past by accident.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

2 participants