From f0abb45dce7fc0ab23eb5b8675168556837d5472 Mon Sep 17 00:00:00 2001 From: Jim Date: Mon, 27 Jul 2015 11:06:58 -0700 Subject: [PATCH] Merge pull request #4469 from KevinTCoughlin/kevintcoughlin/#4265 Fixes #4265 - Clarify React.render note in documentation (cherry picked from commit fab001aa803a7b7d7f76721911305f2c4d2dbb5f) --- docs/docs/ref-01-top-level-api.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/docs/ref-01-top-level-api.md b/docs/docs/ref-01-top-level-api.md index 127df5c3f6..4601c84dfd 100644 --- a/docs/docs/ref-01-top-level-api.md +++ b/docs/docs/ref-01-top-level-api.md @@ -89,9 +89,13 @@ If the optional callback is provided, it will be executed after the component is > Note: > -> `React.render()` replaces the contents of the container node you -> pass in. In the future, it may be possible to insert a component to an -> existing DOM node without overwriting the existing children. +> `React.render()` controls the contents of the container node you pass in. Any existing DOM elements +> inside are replaced when first called. Later calls use React’s DOM diffing algorithm for efficient +> updates. +> +> `React.render()` does not modify the container node (only modifies the children of the container). In +> the future, it may be possible to insert a component to an existing DOM node without overwriting +> the existing children. ### React.unmountComponentAtNode