Skip to content

fix(material-experimental/mdc-chips): removed chip still focusable #18083

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

Merged
merged 1 commit into from
Jan 8, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jan 1, 2020

When an MDC chip is removed it gets transitioned to width: 0, but it's up to the consumer to remove it from the DOM. This means that it's possible for the user to tab into it. These changes add display: none after the animation is done so the element becomes non-focusable.

When an MDC chip is removed it gets transitioned to `width: 0`, but it's up to the consumer to remove it from the DOM. This means that it's possible for the user to tab into it. These changes add `display: none` after the animation is done so the element becomes non-focusable.
@crisbeto crisbeto added pr: merge safe P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release labels Jan 1, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner January 1, 2020 15:29
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 1, 2020
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: merge safe labels Jan 1, 2020
@mmalerba
Copy link
Contributor

mmalerba commented Jan 1, 2020

LGTM, not merge safe though, since this is used internally

@mmalerba mmalerba merged commit 403377d into angular:master Jan 8, 2020
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
…lar#18083)

When an MDC chip is removed it gets transitioned to `width: 0`, but it's up to the consumer to remove it from the DOM. This means that it's possible for the user to tab into it. These changes add `display: none` after the animation is done so the element becomes non-focusable.
@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 Feb 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants