Skip to content

fix(a11y): list key manager not emitting change event if new item is added to active index #19666

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

Currently we emit the ListKeyManager.change event if the active index changes, but the problem is that the list could be swapped out, resulting in a new item at the same index. These changes switch to using the item reference to determine whether we need to emit the event.

Fixes #19661.

…added to active index

Currently we emit the `ListKeyManager.change` event if the active index changes, but the problem is that the list could be swapped out, resulting in a new item at the same index. These changes switch to using the item reference to determine whether we need to emit the event.

Fixes angular#19661.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jun 16, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 16, 2020
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 lgtm action: merge The PR is ready for merge by the caretaker labels Jun 16, 2020
@jelbourn jelbourn merged commit 3fbebe0 into angular:master Jun 29, 2020
jelbourn pushed a commit that referenced this pull request Jun 29, 2020
…added to active index (#19666)

Currently we emit the `ListKeyManager.change` event if the active index changes, but the problem is that the list could be swapped out, resulting in a new item at the same index. These changes switch to using the item reference to determine whether we need to emit the event.

Fixes #19661.
@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 Jul 30, 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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent 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(Autocomplete): (optionActivated) not triggered when [autoActiveFirstOption] and option list changes
3 participants