From a9239a586e7d0d9cdb7b2f0e42de5ca4023f35e7 Mon Sep 17 00:00:00 2001 From: Wojciech Golaszewski Date: Thu, 12 Nov 2020 13:18:19 +0100 Subject: [PATCH] More explicit docs about uncontrolled forms. (#3382) --- content/docs/uncontrolled-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/uncontrolled-components.md b/content/docs/uncontrolled-components.md index 54b729e9..e6680462 100644 --- a/content/docs/uncontrolled-components.md +++ b/content/docs/uncontrolled-components.md @@ -45,7 +45,7 @@ If it's still not clear which type of component you should use for a particular ### Default Values {#default-values} -In the React rendering lifecycle, the `value` attribute on form elements will override the value in the DOM. With an uncontrolled component, you often want React to specify the initial value, but leave subsequent updates uncontrolled. To handle this case, you can specify a `defaultValue` attribute instead of `value`. +In the React rendering lifecycle, the `value` attribute on form elements will override the value in the DOM. With an uncontrolled component, you often want React to specify the initial value, but leave subsequent updates uncontrolled. To handle this case, you can specify a `defaultValue` attribute instead of `value`. Changing the value of `defaultValue` attribute after a component has mounted will not cause any update of the value in the DOM. ```javascript{7} render() {