-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(input/testing): unable to set the value of inputs that don't respond to typing #18812
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(input/testing): unable to set the value of inputs that don't respond to typing #18812
Conversation
80d7670
to
34bc6de
Compare
34bc6de
to
72ef642
Compare
@mmalerba I've reworked this based on our discussion. I'm also bumping up the priority since the issue has come up multiple times. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ond to typing The `setValue` method of the input harness is set up so that it types out the value in the input. This won't work for input that don't respond to typing (e.g. `color`). These changes add an extra call that also sets the `value` property of the input, on top of typing into it. Fixes angular#18790.
72ef642
to
ccab78c
Compare
…ond to typing (#18812) The `setValue` method of the input harness is set up so that it types out the value in the input. This won't work for input that don't respond to typing (e.g. `color`). These changes add an extra call that also sets the `value` property of the input, on top of typing into it. Fixes #18790.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
The
setValue
method of the input harness is set up so that it types out the value in the input. This won't work for inputs that don't respond to typing (e.g.color
). These changes add an extra call that also sets thevalue
property of the input, on top of typing into it.Fixes #18790.
Note: not sure whether the change to the
TestElement
signature needs to be made optional first.