Tweaks to new content in forms documentation
Paul O’Shannessy committed
Jul 16, 2015 at 23:47 UTC
2b97bc63f049f46e38c4d0369ed22a8adb509aef
1 file changed
+6
-2
docs/docs/07-forms.md
+6
-2
@@ -81,7 +81,7 @@ An `<input>` that does not supply a `value` (or sets it to `null`) is an *uncont
81
82
This will render an input that starts off with an empty value. Any user input will be immediately reflected by the rendered element. If you wanted to listen to updates to the value, you could use the `onChange` event just like you can with controlled components.
83
84
-###Default Value
84
+### Default Value
85
86
If you want to initialize the component with a non-empty value, you can supply a `defaultValue` prop. For example:
87
@@ -91,10 +91,14 @@ If you want to initialize the component with a non-empty value, you can supply a
91
}
92
```
93
94
-This example will function much like the **Controlled Components** example above. *Note:* the defaultValue prop is only applied when the component mounts for the first time. If you need to programmatically update the value after initial mount, you will need to use a controlled component (see section on controlled components).
94
+This example will function much like the **Controlled Components** example above.
95
96
Likewise, `<input>` supports `defaultChecked` and `<select>` supports `defaultValue`.
97
98
+> Note:
99
+>
100
+> The `defaultValue` and `defaultChecked` props are only used during initial render. If you need to update the value in a subsequent render, you will need to use a [controlled component](#controlled-components).
101
+
102
103
## Advanced Topics
104