Skip to content

fix(aria-describer): exception when attempting to describe a non-element node #9392

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

Conversation

crisbeto
Copy link
Member

  • Fixes an error that was being thrown when trying to describe a non-element node. This could happen if the consumer is attempting to describe an ng-container which corresponds to a comment node.
  • Switches a few cases, that had hard-coded the Node.ELEMENT_NODE constant for to Universal compatibility, to take the constant from the Document.

Relates to #8724.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 15, 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 pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jan 16, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jan 16, 2018
@josephperrott
Copy link
Member

needs rebase

@josephperrott josephperrott added pr: needs rebase and removed action: merge The PR is ready for merge by the caretaker labels Jan 19, 2018
…ent node

* Fixes an error that was being thrown when trying to describe a non-element node. This could happen if the consumer is attempting to describe an `ng-container` which corresponds to a comment node.
* Switches a few cases, that had hard-coded the `Node.ELEMENT_NODE` constant for to Universal compatibility, to take the constant from the `Document`.

Relates to angular#8724.
@crisbeto crisbeto force-pushed the 8724/aria-describer-non-element-node branch from 484a285 to 083d287 Compare January 19, 2018 20:05
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed pr: needs rebase labels Jan 19, 2018
@crisbeto
Copy link
Member Author

Rebased.

@jelbourn jelbourn merged commit 4c7a4f3 into angular:master Jan 23, 2018
@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
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants