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(badge): incorrectly setting aria-describedby #9957

Merged
merged 1 commit into from
Feb 18, 2018

Conversation

crisbeto
Copy link
Member

  • With the current setup, the badge component will set an aria-describedby message that doesn't correspond to the actual description, because it does the describing before its description has been updated. These changes make it so it uses the actual description.
  • Fixes the aria description not being removed once the badge is destroyed.
  • Cleans up the badge testing setup.

* With the current setup, the badge component will set an `aria-describedby` message that doesn't correspond to the actual description, because it does the describing before its description has been updated. These changes make it so it uses the actual description.
* Fixes the aria description not being removed once the badge is destroyed.
* Cleans up the badge testing setup.
@crisbeto crisbeto added pr: needs review Accessibility This issue is related to accessibility (a11y) labels Feb 14, 2018
@crisbeto crisbeto requested a review from amcdnl as a code owner February 14, 2018 19:43
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 14, 2018
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 target: major This PR is targeted for the next major release pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Feb 14, 2018
crisbeto added a commit to crisbeto/material2 that referenced this pull request Feb 14, 2018
Currently the `AriaDescriber` assumes that any values being described are going to be strings, however that may not be the case if a value is being passed it directly from the view. These changes add an extra check in order to avoid having to do null checks on consumption (see angular#9957).
Copy link
Contributor

@amcdnl amcdnl 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 pushed a commit that referenced this pull request Feb 18, 2018
Currently the `AriaDescriber` assumes that any values being described are going to be strings, however that may not be the case if a value is being passed it directly from the view. These changes add an extra check in order to avoid having to do null checks on consumption (see #9957).
@jelbourn jelbourn merged commit aed7e8a into angular:master Feb 18, 2018
tinayuangao pushed a commit that referenced this pull request Feb 20, 2018
Currently the `AriaDescriber` assumes that any values being described are going to be strings, however that may not be the case if a value is being passed it directly from the view. These changes add an extra check in order to avoid having to do null checks on consumption (see #9957).
tinayuangao pushed a commit that referenced this pull request Feb 20, 2018
* With the current setup, the badge component will set an `aria-describedby` message that doesn't correspond to the actual description, because it does the describing before its description has been updated. These changes make it so it uses the actual description.
* Fixes the aria description not being removed once the badge is destroyed.
* Cleans up the badge testing setup.
andrewseguin pushed a commit that referenced this pull request Feb 20, 2018
Currently the `AriaDescriber` assumes that any values being described are going to be strings, however that may not be the case if a value is being passed it directly from the view. These changes add an extra check in order to avoid having to do null checks on consumption (see #9957).
@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 Sep 8, 2019
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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants