From fe5be8b288d6e0704a79766fd8f190d219b4b16e Mon Sep 17 00:00:00 2001 From: felher Date: Tue, 9 Jul 2024 05:18:37 +0200 Subject: [PATCH] Fix typo in documentation.md (#160) --- website/docs/documentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/documentation.md b/website/docs/documentation.md index 9606a55..a685720 100644 --- a/website/docs/documentation.md +++ b/website/docs/documentation.md @@ -1832,7 +1832,7 @@ So here are the events that work in all browsers of interest: ### Controlled Inputs Caveats -* You can't have conflicting `controlled` blocks on the same element. You also can't have a `value <-- ???` binder outside of a controlled block on an element that already has `value` controlled. Trying to do that will throw and exception. If the `controlled` block is added to the element, it defines the sole source of truth for the `value` prop. +* You can't have conflicting `controlled` blocks on the same element. You also can't have a `value <-- ???` binder outside of a controlled block on an element that already has `value` controlled. Trying to do that will throw an exception. If the `controlled` block is added to the element, it defines the sole source of truth for the `value` prop. * The `onInput` (or `onClick` etc.) event listener defined inside of the `controlled` block will be run before any other event listeners on this element, even if you registered those other listeners before adding the controlled block. If the controlled block is added to an element after it has already been mounted, under the hood this is achieved by removing all the Laminar listeners from the element and re-adding them in the same relative order, but **after** the controlled event listener. This is done to ensure that other event listeners do not interfere with the controlled input functionality (e.g. by stopping propagation of the event).