Tree: 3604354776

lukechilds-patch-1

main

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '3604354776'

${ noResults }

Commit Graph

9 Commits (36043547760c1239ce78b51c92a48e336a7362b6)

Author	SHA1	Message	Date
Julen Ruiz Aizpuru	3ebec4b55b	Docs: do not render components to `document.body` Rendering to `document.body` in the examples is conveniently short, but it can be misleading at the same time, especially for newcomers. While it's possible to render React components to `document.body`, any 3rd party scripts can also mess up with it, and it can have unintended consequences and be source of difficult-to-trace bugs.	10 years ago
Patrick Laughlin	d1eda2cb43	Update 06-transferring-props.md	10 years ago
Kirk Steven Hansen	de43169c6b	Typo in first commit.	10 years ago
Kirk Steven Hansen	e4d4cd3e59	Updated tutorial to be more clear about the dependence on the --harmony flag.	10 years ago
cookfront	83d5a4514d	The same problem in issue #2648	10 years ago
张敏	e693d3f321	In `Transferring Props` guide, `Manual Transfer` section will lead an error ```c var FancyCheckbox = React.createClass({ render: function() { var fancyClass = this.props.checked ? 'FancyChecked' : 'FancyUnchecked'; return ( <div className={fancyClass} onClick={this.props.onClick}> {this.props.children} </div> ); } }); React.render( <FancyCheckbox checked={true} onClick={console.log}> Hello world! </FancyCheckbox>, document.body ); ``` When click `Hello world!` will lead a `Uncaught TypeError: Illegal invocation` error	10 years ago
Stefan Dombrowski	26ad3053c5	React.renderComponent --> React.render Also fixed a spelling mistake.	10 years ago
Sebastian Markbage	4202fcd9c5	Replace transferPropsTo with transferring props patterns	10 years ago