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

fix(material/chips): handle matChipRemove set on a button #23538

Merged
merged 1 commit into from Sep 10, 2021

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 6, 2021

Fixes that matChipRemove looked off when it's set on a button element. Also updates all the examples to use buttons.

Note that we don't need any extra logic, because the MatChipRemove directive already sets type="button" when it's applied to a button element.

Fixes #23463.

Fixes that `matChipRemove` looked off when it's set on a `button` element. Also updates all the examples to use buttons.

Note that we don't need any extra logic, because the `MatChipRemove` directive already sets `type="button"` when it's applied to a `button` element.

Fixes angular#23463.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Sep 6, 2021
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 6, 2021
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added Accessibility This issue is related to accessibility (a11y) action: merge The PR is ready for merge by the caretaker labels Sep 7, 2021
@andrewseguin andrewseguin merged commit bb9c36b into angular:master Sep 10, 2021
andrewseguin pushed a commit that referenced this pull request Sep 10, 2021
Fixes that `matChipRemove` looked off when it's set on a `button` element. Also updates all the examples to use buttons.

Note that we don't need any extra logic, because the `MatChipRemove` directive already sets `type="button"` when it's applied to a `button` element.

Fixes #23463.

(cherry picked from commit bb9c36b)
@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 Oct 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(chips): matChipRemove should not apply to icons
3 participants