Skip to content
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

refactor(angular/input): inconsistently reading name from input with ngModel #1028

Merged
merged 1 commit into from
Jan 17, 2022

Conversation

jeripeierSBB
Copy link
Collaborator

@jeripeierSBB jeripeierSBB commented Jan 17, 2022

If an input has a name binding and an ngModel, the input harness won't be able to
read the name from the DOM, because ngModel doesn't proxy it. These changes add
the proxy behavior to the SbbInput directive, similarly to what we we're doing for
required, placeholder, readonly etc.
angular/components#19233

…ngModel (#19233)

If an input has a `name` binding and an `ngModel`, the input harness won't be able to
read the name from the DOM, because `ngModel` doesn't proxy it. These changes add
the proxy behavior to the `MatInput` directive, similarly to what we we're doing for
`required`, `placeholder`, `readonly` etc.
angular/components#19233
@jeripeierSBB jeripeierSBB changed the title refactor(angular/input): inconsistently reading name from input with … refactor(angular/input): inconsistently reading name from input with ngModel Jan 17, 2022
@github-actions
Copy link

Staging ready from 6dd86ed at 1/17/2022, 7:56:24 AM:

Copy link
Collaborator

@kyubisation kyubisation left a comment

Choose a reason for hiding this comment

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

LGTM 👍
MatInput is used in the commit message

@jeripeierSBB jeripeierSBB merged commit 939eb69 into master Jan 17, 2022
@jeripeierSBB jeripeierSBB deleted the input-change branch January 17, 2022 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants