Skip to content

fix(radio): ng-touched incorrectly being set on click #12560

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

devversion
Copy link
Member

@devversion devversion commented Aug 7, 2018

  • The ControlValueAccessor onTouched should be just called if a radio-button blurred. Right now, the ng-touched state will be immediately set if someone presses SPACE or clicks on a radio-button.

@devversion devversion added the target: patch This PR is targeted for the next patch release label Aug 7, 2018
@devversion devversion requested a review from jelbourn as a code owner August 7, 2018 08:44
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 7, 2018
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 7, 2018
@devversion devversion force-pushed the fix/radio-button-ng-touched-click branch from cc87f0a to 9c83797 Compare August 17, 2018 05:57
@devversion devversion added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Aug 27, 2018
@jelbourn jelbourn added P2 The issue is important to a large percentage of users, with a workaround and removed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Sep 16, 2018
@devversion devversion force-pushed the fix/radio-button-ng-touched-click branch from 9c83797 to 49eea2b Compare November 8, 2018 19:56
* The `ControlValueAccessor` `onTouched` should be just called if a radio-button blurred. Right now, the `ng-touched` state will be immediately set if someone presses SPACE or clicks on a radio-button.
@devversion devversion force-pushed the fix/radio-button-ng-touched-click branch from 49eea2b to 9ca18d5 Compare November 10, 2018 08:44
@josephperrott josephperrott merged commit 2f61607 into angular:master Mar 7, 2019
josephperrott pushed a commit that referenced this pull request Mar 7, 2019
* The `ControlValueAccessor` `onTouched` should be just called if a radio-button blurred. Right now, the `ng-touched` state will be immediately set if someone presses SPACE or clicks on a radio-button.
@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 10, 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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants