You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: aio/content/guide/forms.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ In the course of this tutorial, you bind a sample form to data and handle user i
93
93
* Add custom CSS to provide visual feedback on the status.
94
94
* Show and hide validation-error messages.
95
95
4. Respond to a native HTML button-click event by adding to the model data.
96
-
5. Handle form submission using the [`ngSubmit`(api/forms/NgForm#properties)] output property of the form.
96
+
5. Handle form submission using the [`ngSubmit`](api/forms/NgForm#properties) output property of the form.
97
97
* Disable the **Submit** button until the form is valid.
98
98
* After submit, swap out the finished form for different content on the page.
99
99
@@ -467,7 +467,7 @@ You will bind the form property that indicates its overall validity to the **Sub
467
467
3. Run the application now. Notice that the button is enabled—although
468
468
it doesn't do anything useful yet.
469
469
470
-
4. Delete the **Name** value. This violates the "required" rule, so it displays the error message&emdash;and notice that it also disables the **Submit** button.
470
+
4. Delete the **Name** value. This violates the "required" rule, so it displays the error message—and notice that it also disables the **Submit** button.
471
471
472
472
473
473
You didn't have to explicitly wire the button's enabled state to the form's validity.
0 commit comments