{"patch":"diff --git a\/docs\/_posts\/2014-02-20-react-v0.9.md b\/docs\/_posts\/2014-02-20-react-v0.9.md\nnew file mode 100644\nindex 0000000000..0a1b6526d0\n--- \/dev\/null\n+++ b\/docs\/_posts\/2014-02-20-react-v0.9.md\n@@ -0,0 +1,144 @@\n+---\n+title: React v0.9\n+layout: post\n+author: Ben Alpert\n+---\n+\n+I'm excited to announce that today we're releasing React v0.9, which incorporates many bug fixes and several new features since the last release. This release contains almost four months of work, including over 800 commits from over 70 committers!\n+\n+Thanks to everyone who tested the release candidate; we were able to find and fix an error in the event handling code, we upgraded envify to make running browserify on React faster, and we added support for five new attributes.\n+\n+As always, the release is available for download from the CDN:\n+\n+* **React** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **React with Add-Ons** \n+ Dev build with warnings: \n+ Minified build for production: \n+* **In-Browser JSX Transformer** \n+ \n+\n+We've also published version `0.9.0` of the `react` and `react-tools` packages on npm and the `react` package on bower.\n+\n+## What’s New?\n+\n+This version includes better support for normalizing event properties across all supported browsers so that you need to worry even less about cross-browser differences. We've also made many improvements to error messages and have refactored the core to never rethrow errors, so stack traces are more accurate and Chrome's purple break-on-error stop sign now works properly.\n+\n+We've also added to the add-ons build [React.addons.TestUtils](\/react\/docs\/test-utils.html), a set of new utilities to help you write unit tests for React components. You can now simulate events on your components, and several helpers are provided to help make assertions about the rendered DOM tree.\n+\n+We've also made several other improvements and a few breaking changes; the full changelog is provided below.\n+\n+## JSX Whitespace\n+\n+In addition to the changes to React core listed below, we've made a small change to the way JSX interprets whitespace to make things more consistent. With this release, space between two components on the same line will be preserved, while a newline separating a text node from a tag will be eliminated in the output. Consider the code:\n+\n+```html\n+

\n+ Monkeys:\n+ {listOfMonkeys} {submitButton}\n+<\/div>\n+```\n+\n+In v0.8 and below, it was transformed to the following:\n+\n+```javascript\n+React.DOM.div(null,\n+ \" Monkeys: \",\n+ listOfMonkeys, submitButton\n+)\n+```\n+\n+In v0.9, it will be transformed to this JS instead:\n+\n+```javascript{2,3}\n+React.DOM.div(null,\n+ \"Monkeys:\",\n+ listOfMonkeys, \" \", submitButton\n+)\n+```\n+\n+We believe this new behavior is more helpful and elimates cases where unwanted whitespace was previously added.\n+\n+In cases where you want to preserve the space adjacent to a newline, you can write `{'Monkeys: '}` or `Monkeys:{' '}` in your JSX source. We've included a script to do an automated codemod of your JSX source tree that preserves the old whitespace behavior by adding and removing spaces appropriately. You can [install jsx\\_whitespace\\_transformer from npm](https:\/\/github.com\/facebook\/react\/blob\/master\/npm-jsx_whitespace_transformer\/README.md) and run it over your source tree to modify files in place. The transformed JSX files will preserve your code's existing whitespace behavior.\n+\n+## Changelog\n+\n+### React Core\n+\n+#### Breaking Changes\n+\n+- The lifecycle methods `componentDidMount` and `componentDidUpdate` no longer receive the root node as a parameter; use `this.getDOMNode()` instead\n+- Whenever a prop is equal to `undefined`, the default value returned by `getDefaultProps` will now be used instead\n+- `React.unmountAndReleaseReactRootNode` was previously deprecated and has now been removed\n+- `React.renderComponentToString` is now synchronous and returns the generated HTML string\n+- Full-page rendering (that is, rendering the `` tag using React) is now supported only when starting with server-rendered markup\n+- On mouse wheel events, `deltaY` is no longer negated\n+- When prop types validation fails, a warning is logged instead of an error thrown (with the production build of React, type checks are now skipped for performance)\n+- On `input`, `select`, and `textarea` elements, `.getValue()` is no longer supported; use `.getDOMNode().value` instead\n+\n+#### New Features\n+\n+- React now never rethrows errors, so stack traces are more accurate and Chrome's purple break-on-error stop sign now works properly\n+- Added support for SVG tags `defs`, `linearGradient`, `polygon`, `radialGradient`, `stop`\n+- Added support for more attributes:\n+ - `crossOrigin` for CORS requests\n+ - `download` and `hrefLang` for `` tags\n+ - `mediaGroup` and `muted` for `

dillon1000/react

Files changed