Skip to content

fix(select): indicating programmatic value change as user interaction in some cases #19970

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
Jul 24, 2020

Conversation

crisbeto
Copy link
Member

We were using ListKeyManager.setActiveItem to change the active item when a value is assigned through a FormControl, in order to have it be highlighted if the user opens the panel. The problem is that setActiveItem emits a change event as if it's coming from the user, causing us to dispatch an event object with isUserInput: true.

These changes use updateActiveItem instead which only updates the item, but doesn't emit any events.

Fixes #19967.

… in some cases

We were using `ListKeyManager.setActiveItem` to change the active item when a value is assigned through a `FormControl`, in order to have it be highlighted if the user opens the panel. The problem is that `setActiveItem` emits a change event as if it's coming from the user, causing us to dispatch an event object with `isUserInput: true`.

These changes use `updateActiveItem` instead which only updates the item, but doesn't emit any events.

Fixes angular#19967.
@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 Jul 14, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 14, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker labels Jul 14, 2020
@wagnermaciel wagnermaciel merged commit 316141f into angular:master Jul 24, 2020
wagnermaciel pushed a commit that referenced this pull request Jul 24, 2020
… in some cases (#19970)

We were using `ListKeyManager.setActiveItem` to change the active item when a value is assigned through a `FormControl`, in order to have it be highlighted if the user opens the panel. The problem is that `setActiveItem` emits a change event as if it's coming from the user, causing us to dispatch an event object with `isUserInput: true`.

These changes use `updateActiveItem` instead which only updates the item, but doesn't emit any events.

Fixes #19967.

(cherry picked from commit 316141f)
@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 Aug 24, 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(mat-option): onSelectionChanged emits "isUserInput === true" when changing value programmatically
4 participants