angular: FormsModule: untouched text input is not pristine in IE 11
I’m submitting a … (check one with “x”)
[x ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior When showing a form in IE 11 with an input field, the initial state of the field is not pristine, leading to error messages being shown to the user before he touched the field.
Expected behavior The field state should be pristine until the user first entered and removed some text. This works fine in e.g. Google Chrome
Minimal reproduction of the problem with instructions http://embed.plnkr.co/fm7lH2/ The red error message should only be display when the user entered and removed some text.
What is the motivation / use case for changing the behavior? Form validation errors should only be displayed when a user touched the form.
Please tell us about your environment: Windows 7 / IE 11
-
Angular version: 2.4.7
-
Browser: IE 11
-
Language: TypeScript
-
Node (for AoT issues):
node --version
= v6.3.1
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (13 by maintainers)
Commits related to this issue
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- fix(forms): form controls should have pristine init state in IE Closes #14440 Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode Closes #14667 — committed to DzmitryShylovich/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode (#14679) Closes #14667 PR Close #14679 — committed to SamVerschueren/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode (#14679) Closes #14667 PR Close #14679 — committed to asnowwolf/angular by DzmitryShylovich 7 years ago
- feat(forms): allow to compile forms in strictNullChecks mode (#14679) Closes #14667 PR Close #14679 — committed to juleskremer/angular by DzmitryShylovich 7 years ago
@mmalerba will be fixed here https://github.com/angular/angular/pull/14443 Looks like when
placeholder
property is present IE emits change event with an empty string value.