{"commit":{"authorName":"Paul O’Shannessy","revision":"85372964e50ffe76701377278ba1ac1c6582db4a","authorEmail":"paul@oshannessy.com","shortRevision":"85372964e5","authoredAt":"2016-04-07T13:24:29-07:00","subject":"Update Changelog for v15"},"files":[{"status":"M","path":"CHANGELOG.md"}],"patch":"diff --git a\/CHANGELOG.md b\/CHANGELOG.md\nindex 9b91a675b5..82f9a6c765 100644\n--- a\/CHANGELOG.md\n+++ b\/CHANGELOG.md\n@@ -1,3 +1,87 @@\n+## 15.0.0 (April 7, 2016)\n+\n+### Major changes\n+\n+- **Initial render now uses `document.createElement` instead of generating HTML.** Previously we would generate a large string of HTML and then set `node.innerHTML`. At the time, this was decided to be faster than using `document.createElement` for the majority of cases and browsers that we supported. Browsers have continued to improve and so overwhelmingly this is no longer true. By using `createElement` we can make other parts of React faster. ()[@spicyj](https:\/\/github.com\/spicyj) in [#5205](https:\/\/github.com\/facebook\/react\/pull\/5205))\n+- **`data-reactid` is no longer on every node.** As a result of using `document.createElement`, we can prime the node cache as we create DOM nodes, allowing us to skip a potential lookup (which used the `data-reactid` attribute). Root nodes will have a `data-reactroot` attribute and server generated markup will still contain `data-reactid`. ()[@spicyj](https:\/\/github.com\/spicyj) in [#5205](https:\/\/github.com\/facebook\/react\/pull\/5205))\n+- **No more extra ``s.** ReactDOM will now render plain text nodes interspersed with comment nodes that are used for demarcation. This gives us the same ability to update individual pieces of text, without creating extra nested nodes. If you were targeting these ``s in your CSS, you will need to adjust accordingly. You can always render them explicitly in your components. ([@mwiencek](https:\/\/github.com\/mwiencek) in [#5753](https:\/\/github.com\/facebook\/react\/pull\/5753))\n+- **Rendering `null` now uses comment nodes.** Previously `null` would render to `

`s.**\n+- **`React.cloneElement()` now resolves `defaultProps`.** We fixed a bug in `React.cloneElement()` that some components may rely on. If some of the `props` received by `cloneElement()` are `undefined`, it used to return an element with `undefined` values for those props. We’re changing it to be consistent with `createElement()`. Now any `undefined` props passed to `cloneElement()` are resolved to the corresponding component’s `defaultProps`. ([@truongduy134](https:\/\/github.com\/truongduy134) in [#5997](https:\/\/github.com\/facebook\/react\/pull\/5997))\n+- **`ReactPerf.getLastMeasurements()` is opaque.** This change won’t affect applications but may break some third-party tools. We are [revamping `ReactPerf` implementation](https:\/\/github.com\/facebook\/react\/pull\/6046) and plan to release it during the 15.x cycle. The internal performance measurement format is subject to change so, for the time being, we consider the return value of `ReactPerf.getLastMeasurements()` an opaque data structure that should not be relied upon. ([@gaearon](https:\/\/github.com\/gaearon) in [#6286](https:\/\/github.com\/facebook\/react\/pull\/6286))\n+\n+#### Removed deprecations\n+\n+These deprecations were introduced nine months ago in v0.14 with a warning and are removed:\n+\n+- Deprecated APIs are removed from the `React` top-level export: `findDOMNode`, `render`, `renderToString`, `renderToStaticMarkup`, and `unmountComponentAtNode`. As a reminder, they are now available on `ReactDOM` and `ReactDOMServer`. ([@jimfb](https:\/\/github.com\/jimfb) in [#5832](https:\/\/github.com\/facebook\/react\/pull\/5832))\n+- Deprecated addons are removed: `batchedUpdates` and `cloneWithProps`. ([@jimfb](https:\/\/github.com\/jimfb) in [#5859](https:\/\/github.com\/facebook\/react\/pull\/5859), [@zpao](https:\/\/github.com\/zpao) in [#6016](https:\/\/github.com\/facebook\/react\/pull\/6016))\n+- Deprecated component instance methods are removed: `setProps`, `replaceProps`, and `getDOMNode`. ([@jimfb](https:\/\/github.com\/jimfb) in [#5570](https:\/\/github.com\/facebook\/react\/pull\/5570))\n+- Deprecated CommonJS `react\/addons` entry point is removed. As a reminder, you should use separate `react-addons-*` packages instead. This only applies if you use the CommonJS builds. ([@gaearon](https:\/\/github.com\/gaearon) in [#6285](https:\/\/github.com\/facebook\/react\/pull\/6285))\n+- Passing `children` to void elements like `` was deprecated, and now throws an error. ([@jonhester](https:\/\/github.com\/jonhester) in [#3372](https:\/\/github.com\/facebook\/react\/pull\/3372))\n+- React-specific properties on DOM `refs` (e.g. `this.refs.div.props`) were deprecated, and are removed now. ([@jimfb](https:\/\/github.com\/jimfb) in [#5495](https:\/\/github.com\/facebook\/react\/pull\/5495))\n+\n+### New deprecations, introduced with a warning\n+\n+Each of these changes will continue to work as before with a new warning until the release of React 16 so you can upgrade your code gradually.\n+\n+- `LinkedStateMixin` and `valueLink` are now deprecated due to very low popularity. If you need this, you can use a wrapper component that implements the same behavior: [react-linked-input](https:\/\/www.npmjs.com\/package\/react-linked-input). ([@jimfb](https:\/\/github.com\/jimfb) in [#6127](https:\/\/github.com\/facebook\/react\/pull\/6127))\n+- Future versions of React will treat `` as a request to clear the input. However, React 0.14 has been ignoring `value={null}`. React 15 warns you on a `null` input value and offers you to clarify your intention. To fix the warning, you may explicitly pass an empty string to clear a controlled input, or pass `undefined` to make the input uncontrolled. ([@antoaravinth](https:\/\/github.com\/antoaravinth) in [#5048](https:\/\/github.com\/facebook\/react\/pull\/5048))\n+- `ReactPerf.printDOM()` was renamed to `ReactPerf.printOperations()`, and `ReactPerf.getMeasurementsSummaryMap()` was renamed to `ReactPerf.getWasted()`. ([@gaearon](https:\/\/github.com\/gaearon) in [#6287](https:\/\/github.com\/facebook\/react\/pull\/6287))\n+\n+### New helpful warnings\n+\n+- If you use a minified copy of the _development_ build, React DOM kindly encourages you to use the faster production build instead. ([@spicyj](https:\/\/github.com\/spicyj) in [#5083](https:\/\/github.com\/facebook\/react\/pull\/5083))\n+- React DOM: When specifying a unit-less CSS value as a string, a future version will not add `px` automatically. This version now warns in this case (ex: writing `style={{'{{'}}width: '300'}}`. Unitless *number* values like `width: 300` are unchanged. ([@pluma](https:\/\/github.com\/pluma) in [#5140](https:\/\/github.com\/facebook\/react\/pull\/5140))\n+- Synthetic Events will now warn when setting and accessing properties (which will not get cleared appropriately), as well as warn on access after an event has been returned to the pool. ([@kentcdodds](https:\/\/github.com\/kentcdodds) in [#5940](https:\/\/github.com\/facebook\/react\/pull\/5940) and [@koba04](https:\/\/github.com\/koba04) in [#5947](https:\/\/github.com\/facebook\/react\/pull\/5947))\n+- Elements will now warn when attempting to read `ref` and `key` from the props. ([@prometheansacrifice](https:\/\/github.com\/prometheansacrifice) in [#5744](https:\/\/github.com\/facebook\/react\/pull\/5744))\n+- React will now warn if you pass a different `props` object to `super()` in the constructor. ([@prometheansacrifice](https:\/\/github.com\/prometheansacrifice) in [#5346](https:\/\/github.com\/facebook\/react\/pull\/5346))\n+- React will now warn if you call `setState()` inside `getChildContext()`. ([@raineroviir](https:\/\/github.com\/raineroviir) in [#6121](https:\/\/github.com\/facebook\/react\/pull\/6121))\n+- React DOM now attempts to warn for mistyped event handlers on DOM elements, such as `onclick` which should be `onClick`. ([@ali](https:\/\/github.com\/ali) in [#5361](https:\/\/github.com\/facebook\/react\/pull\/5361))\n+- React DOM now warns about `NaN` values in `style`. ([@jontewks](https:\/\/github.com\/jontewks) in [#5811](https:\/\/github.com\/facebook\/react\/pull\/5811))\n+- React DOM now warns if you specify both `value` and `defaultValue` for an input. ([@mgmcdermott](https:\/\/github.com\/mgmcdermott) in [#5823](https:\/\/github.com\/facebook\/react\/pull\/5823))\n+- React DOM now warns if an input switches between being controlled and uncontrolled. ([@TheBlasfem](https:\/\/github.com\/TheBlasfem) in [#5864](https:\/\/github.com\/facebook\/react\/pull\/5864))\n+- React DOM now warns if you specify `onFocusIn` or `onFocusOut` handlers as they are unnecessary in React. ([@jontewks](https:\/\/github.com\/jontewks) in [#6296](https:\/\/github.com\/facebook\/react\/pull\/6296))\n+- React now prints a descriptive error message when you pass an invalid callback as the last argument to `ReactDOM.render()`, `this.setState()`, or `this.forceUpdate()`. ([@conorhastings](https:\/\/github.com\/conorhastings) in [#5193](https:\/\/github.com\/facebook\/react\/pull\/5193) and [@gaearon](https:\/\/github.com\/gaearon) in [#6310](https:\/\/github.com\/facebook\/react\/pull\/6310))\n+- Add-Ons: `TestUtils.Simulate()` now prints a helpful message if you attempt to use it with shallow rendering. ([@conorhastings](https:\/\/github.com\/conorhastings) in [#5358](https:\/\/github.com\/facebook\/react\/pull\/5358))\n+- PropTypes: `arrayOf()` and `objectOf()` provide better error messages for invalid arguments. ([@chicoxyzzy](https:\/\/github.com\/chicoxyzzy) in [#5390](https:\/\/github.com\/facebook\/react\/pull\/5390))\n+\n+### Notable bug fixes\n+\n+- Fixed multiple small memory leaks. ([@spicyj](https:\/\/github.com\/spicyj) in [#4983](https:\/\/github.com\/facebook\/react\/pull\/4983) and [@victor-homyakov](https:\/\/github.com\/victor-homyakov) in [#6309](https:\/\/github.com\/facebook\/react\/pull\/6309))\n+- Input events are handled more reliably in IE 10 and IE 11; spurious events no longer fire when using a placeholder. ([@jquense](https:\/\/github.com\/jquense) in [#4051](https:\/\/github.com\/facebook\/react\/pull\/4051))\n+- The `componentWillReceiveProps()` lifecycle method is now consistently called when `context` changes. ([@milesj](https:\/\/github.com\/milesj) in [#5787](https:\/\/github.com\/facebook\/react\/pull\/5787))\n+- `React.cloneElement()` doesn’t append slash to an existing `key` when used inside `React.Children.map()`. ([@ianobermiller](https:\/\/github.com\/ianobermiller) in [#5892](https:\/\/github.com\/facebook\/react\/pull\/5892))\n+- React DOM now supports the `cite` and `profile` HTML attributes. ([@AprilArcus](https:\/\/github.com\/AprilArcus) in [#6094](https:\/\/github.com\/facebook\/react\/pull\/6094) and [@saiichihashimoto](https:\/\/github.com\/saiichihashimoto) in [#6032](https:\/\/github.com\/facebook\/react\/pull\/6032))\n+- React DOM now supports `cssFloat`, `gridRow` and `gridColumn` CSS properties. ([@stevenvachon](https:\/\/github.com\/stevenvachon) in [#6133](https:\/\/github.com\/facebook\/react\/pull\/6133) and [@mnordick](https:\/\/github.com\/mnordick) in [#4779](https:\/\/github.com\/facebook\/react\/pull\/4779))\n+- React DOM now correctly handles `borderImageOutset`, `borderImageWidth`, `borderImageSlice`, `floodOpacity`, `strokeDasharray`, and `strokeMiterlimit` as unitless CSS properties. ([@rofrischmann](https:\/\/github.com\/rofrischmann) in [#6210](https:\/\/github.com\/facebook\/react\/pull\/6210) and [#6270](https:\/\/github.com\/facebook\/react\/pull\/6270))\n+- React DOM now supports the `onAnimationStart`, `onAnimationEnd`, `onAnimationIteration`, `onTransitionEnd`, and `onInvalid` events. Support for `onLoad` has been added to `object` elements. ([@tomduncalf](https:\/\/github.com\/tomduncalf) in [#5187](https:\/\/github.com\/facebook\/react\/pull\/5187), [@milesj](https:\/\/github.com\/milesj) in [#6005](https:\/\/github.com\/facebook\/react\/pull\/6005), and [@ara4n](https:\/\/github.com\/ara4n) in [#5781](https:\/\/github.com\/facebook\/react\/pull\/5781))\n+- React DOM now defaults to using DOM attributes instead of properties, which fixes a few edge case bugs. Additionally the nullification of values (ex: `href={null}`) now results in the forceful removal, no longer trying to set to the default value used by browsers in the absence of a value. ([@syranide](https:\/\/github.com\/syranide) in [#1510](https:\/\/github.com\/facebook\/react\/pull\/1510))\n+- React DOM does not mistakingly coerce `children` to strings for Web Components. ([@jimfb](https:\/\/github.com\/jimfb) in [#5093](https:\/\/github.com\/facebook\/react\/pull\/5093))\n+- React DOM now correctly normalizes SVG `` events. ([@edmellum](https:\/\/github.com\/edmellum) in [#5720](https:\/\/github.com\/facebook\/react\/pull\/5720))\n+- React DOM does not throw if a `

dillon1000/react

Files changed