From 44a4d13badebeebc5ecde16b202b5cbeba953eb7 Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Fri, 8 Apr 2022 10:39:27 -0400 Subject: [PATCH] update note --- docs/getting-started/form-controls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/form-controls.md b/docs/getting-started/form-controls.md index 8aa1eb8d8..0398b4f4e 100644 --- a/docs/getting-started/form-controls.md +++ b/docs/getting-started/form-controls.md @@ -8,7 +8,7 @@ Shoelace solves this problem by using the [`formdata`](https://developer.mozilla ## A Note About Event Handling -Shoelace uses event listeners to intercept the form's `formdata` and `submit` events. This allows it to inject form data and activate client-side validation as necessary. If you're also using an event listener, this means _you must attach the listener after Shoelace form controls are connected to the DOM_. Otherwise, your logic will run before Shoelace has a chance to inject form data and validate form controls. +Shoelace uses event listeners to intercept the form's `formdata` and `submit` events. This allows it to inject data and trigger validation as necessary. If you're also attaching an event listener to the form, _you must attach it after Shoelace form controls are connected to the DOM_, otherwise your logic will run before Shoelace has a chance to inject form data and validate form controls. ## Form Serialization