From 2b97bc63f049f46e38c4d0369ed22a8adb509aef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Thu, 16 Jul 2015 23:47:50 -0700 Subject: [PATCH] Tweaks to new content in forms documentation --- docs/docs/07-forms.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/docs/07-forms.md b/docs/docs/07-forms.md index 938d5f6c2b..9cdc0d27af 100644 --- a/docs/docs/07-forms.md +++ b/docs/docs/07-forms.md @@ -81,7 +81,7 @@ An `` that does not supply a `value` (or sets it to `null`) is an *uncont 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. -###Default Value +### Default Value If you want to initialize the component with a non-empty value, you can supply a `defaultValue` prop. For example: @@ -91,10 +91,14 @@ If you want to initialize the component with a non-empty value, you can supply a } ``` -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). +This example will function much like the **Controlled Components** example above. Likewise, `` supports `defaultChecked` and `