React v15
https://github.com/facebook/react
React
- Backport support for the new JSX transform to 15.x. (@lunaruan in #18299 and @gaearon in #20024)
15.6.2 (September 25, 2017)
All Packages
- Switch from BSD + Patents to MIT license
React DOM
- Fix a bug where modifying
document.documentMode
would trigger IE detection in other browsers, breaking change events. (@aweary in #10032) - CSS Columns are treated as unitless numbers. (@aweary in #10115)
- Fix bug in QtWebKit when wrapping synthetic events in proxies. (@walrusfruitcake in #10115)
- Prevent event handlers from receiving extra argument in development. (@aweary in #10115)
- Fix cases where
onChange
would not fire withdefaultChecked
on radio inputs. (@jquense in #10156) - Add support for
controlList
attribute to DOM property whitelist (@nhunzaker in #9940) - Fix a bug where creating an element with a ref in a constructor did not throw an error in development. (@iansu in #10025)
15.6.0 (June 13, 2017)
React
- Downgrade deprecation warnings to use
console.warn
instead ofconsole.error
. (@flarnie in #9753) - Add a deprecation warning for
React.createClass
. Points users tocreate-react-class
instead. (@flarnie in #9771) - Add deprecation warnings and separate module for
React.DOM
factory helpers. (@nhunzaker in #8356) - Warn for deprecation of
React.createMixin
helper, which was never used. (@aweary in #8853)
React DOM
- Add support for CSS variables in
style
attribute. (@aweary in #9302) - Add support for CSS Grid style properties. (@ericsakmar in #9185)
- Fix bug where inputs mutated value on type conversion. (@nhunzaker in #9806)
- Fix issues with
onChange
not firing properly for some inputs. (@jquense in #8575) - Fix bug where controlled number input mistakenly allowed period. (@nhunzaker in #9584)
- Fix bug where performance entries were being cleared. (@chrisui in #9451)
React Addons
- Fix AMD support for addons depending on
react
. (@flarnie in #9919) - Fix
isMounted()
to returntrue
incomponentWillUnmount
. (@mridgway in #9638) - Fix
react-addons-update
to not depend on nativeObject.assign
. (@gaearon in #9937) - Remove broken Google Closure Compiler annotation from
create-react-class
. (@gaearon in #9933) - Remove unnecessary dependency from
react-linked-input
. (@gaearon in #9766) - Point
react-addons-(css-)transition-group
to the new package. (@gaearon in #9937)
15.5.3 (April 7, 2017)
Note: this release has a critical issue and was deprecated. Please update to 15.5.4 or higher.
React Addons
15.5.2 (April 7, 2017)
Note: this release has a critical issue and was deprecated. Please update to 15.5.4 or higher.
React Addons
15.5.0 (April 7, 2017)
Note: this release has a critical issue and was deprecated. Please update to 15.5.4 or higher.
React
- Added a deprecation warning for
React.createClass
. Points users to create-react-class instead. (@acdlite in d9a4fa4) - Added a deprecation warning for
React.PropTypes
. Points users to prop-types instead. (@acdlite in 043845c) - Fixed an issue when using
ReactDOM
together withReactDOMServer
. (@wacii in #9005) - Fixed issue with Closure Compiler. (@anmonteiro in #8895)
- Another fix for Closure Compiler. (@Shastel in #8882)
- Added component stack info to invalid element type warning. (@n3tr in #8495)
React DOM
- Fixed Chrome bug when backspacing in number inputs. (@nhunzaker in #7359)
- Added
react-dom/test-utils
, which exports the React Test Utils. (@bvaughn)
React Test Renderer
- Fixed bug where
componentWillUnmount
was not called for children. (@gre in #8512) - Added
react-test-renderer/shallow
, which exports the shallow renderer. (@bvaughn)
React Addons
- Last release for addons; they will no longer be actively maintained.
- Removed
peerDependencies
so that addons continue to work indefinitely. (@acdlite and @bvaughn in 8a06cd7 and 67a8db3) - Updated to remove references to
React.createClass
andReact.PropTypes
(@acdlite in 12a96b9) react-addons-test-utils
is deprecated. Usereact-dom/test-utils
andreact-test-renderer/shallow
instead. (@bvaughn)
15.4.2 (January 6, 2017)
React
- Fixed build issues with the Brunch bundler. (@gaearon in #8686)
- Improved error messages for invalid element types. (@spicyj in #8612)
- Removed a warning about
getInitialState
whenthis.state
is set. (@bvaughn in #8594) - Removed some dead code. (@diegomura in #8050, @dfrownfelter in #8597)
React DOM
- Fixed a decimal point issue on uncontrolled number inputs. (@nhunzaker in #7750)
- Fixed rendering of textarea placeholder in IE11. (@aweary in #8020)
- Worked around a script engine bug in IE9. (@eoin in #8018)
React Addons
- Fixed build issues in RequireJS and SystemJS environments. (@gaearon in #8686)
- Added missing package dependencies. (@kweiberth in #8467)
React
- React package and browser build no longer "secretly" includes React DOM. (@sebmarkbage in #7164 and #7168)
- Required PropTypes now fail with specific messages for null and undefined. (@chenglou in #7291)
- Improved development performance by freezing children instead of copying. (@keyanzhang in #7455)
React DOM
- Fixed occasional test failures when React DOM is used together with shallow renderer. (@goatslacker in #8097)
- Added a warning for invalid
aria-
attributes. (@jessebeach in #7744) - Added a warning for using
autofocus
rather thanautoFocus
. (@hkal in #7694) - Removed an unnecessary warning about polyfilling
String.prototype.split
. (@nhunzaker in #7629) - Clarified the warning about not calling PropTypes manually. (@jedwards1211 in #7777)
- The unstable
batchedUpdates
API now passes the wrapped function's return value through. (@bgnorlov in #7444) - Fixed a bug with updating text in IE 8. (@mnpenner in #7832)
React Perf
- When ReactPerf is started, you can now view the relative time spent in components as a chart in Chrome Timeline. (@gaearon in #7549)
React Test Utils
- If you call
Simulate.click()
on a<input disabled onClick={foo} />
thenfoo
will get called whereas it didn't before. (@nhunzaker in #7642)
React Test Renderer
- Due to packaging changes, it no longer crashes when imported together with React DOM in the same file. (@sebmarkbage in #7164 and #7168)
ReactTestRenderer.create()
now accepts{createNodeMock: element => mock}
as an optional argument so you can mock refs with snapshot testing. (@Aweary in #7649, #8261)
React
React DOM
- Add
playsInline
to supported HTML attributes. (@reaperhulk in #7519) - Add
as
to supported HTML attributes. (@kevinslin in #7582) - Improve DOM nesting validation warning about whitespace. (@spicyj in #7515)
- Avoid "Member not found" exception in IE10 when calling
preventDefault()
in Synthetic Events. (@g-palmer in #7411) - Fix memory leak in
onSelect
implementation. (@AgtLucas in #7533) - Improve robustness of
document.documentMode
checks to handle Google Tag Manager. (@SchleyB in #7594) - Add more cases to controlled inputs warning. (@marcin-mazurek in #7544)
- Handle case of popup blockers overriding
document.createEvent
. (@Andarist in #7621) - Fix issue with
dangerouslySetInnerHTML
and SVG in Internet Explorer. (@zpao in #7618) - Improve handling of Japanese IME on Internet Explorer. (@msmania in #7107)
React Test Renderer
- Support error boundaries. (@millermedeiros in #7558, #7569, #7619)
- Skip null ref warning. (@Aweary in #7658)
React Perf Add-on
React
- Improve performance of development builds in various ways. (@gaearon in #7461, #7463, #7483, #7488, #7491, #7510)
- Cleanup internal hooks to improve performance of development builds. (@gaearon in #7464, #7472, #7481, #7496)
- Upgrade fbjs to pick up another performance improvement from @gaearon for development builds. (@zpao in #7532)
- Improve startup time of React in Node. (@zertosh in #7493)
- Improve error message of
React.Children.only
. (@spicyj in #7514)
React DOM
- Avoid
<input>
validation warning from browsers when changingtype
. (@nhunzaker in #7333) - Avoid "Member not found" exception in IE10 when calling
stopPropagation()
in Synthetic Events. (@nhunzaker in #7343) - Fix issue resulting in inability to update some
<input>
elements in mobile browsers. (@keyanzhang in #7397) - Fix memory leak in server rendering. (@keyanzhang in #7410)
- Fix issue resulting in
<input type="range">
values not updating when changingmin
ormax
. (@troydemonbreun in #7486) - Add new warning for rare case of attempting to unmount a container owned by a different copy of React. (@ventuno in #7456)
React Test Renderer
React Native Renderer
- Change
trackedTouchCount
invariant into a console.error for better reliability. (@yungsters in #7400)
React
- Add
React.PureComponent
- a new base class to extend, replacingreact-addons-pure-render-mixin
now that mixins don't work with ES2015 classes. (@spicyj in #7195) - Add new warning when modifying
this.props.children
. (@jimfb in #7001) - Fixed issue with ref resolution order. (@gaearon in #7101)
- Warn when mixin is undefined. (@swaroopsm in #6158)
- Downgrade "unexpected batch number" invariant to a warning. (@spicyj in #7133)
- Validate arguments to
oneOf
andoneOfType
PropTypes sooner. (@troydemonbreun in #6316) - Warn when calling PropTypes directly. (@Aweary in #7132, #7194)
- Improve warning when using Maps as children. (@keyanzhang in #7260)
- Add additional type information to the
PropTypes.element
warning. (@alexzherdev in #7319) - Improve component identification in no-op
setState
warning. (@keyanzhang in #7326)
React DOM
- Fix issue with nested server rendering. (@Aweary in #7033)
- Add
xmlns
,xmlnsXlink
to supported SVG attributes. (@salzhrani in #6471) - Add
referrerPolicy
to supported HTML attributes. (@Aweary in #7274) - Fix issue resulting in
<input type="range">
initial value being rounded. (@troydemonbreun in #7251)
React Test Renderer
- Initial public release of package allowing more focused testing. Install with
npm install react-test-renderer
. (@spicyj in #6944, #7258, @iamdustan in #7362)
React Perf Add-on
- Fix issue resulting in excessive warnings when encountering an internal measurement error. (@sassanh in #7299)
React TestUtils Add-on
React
- Fix errant warning about missing React element. (@gaearon in #7193)
- Better removal of dev-only code, leading to a small reduction in the minified production bundle size. (@gaearon in #7188, #7189)
React DOM
- Add stack trace to null input value warning. (@jimfb in #7040)
- Fix webcomponents example. (@jalexanderfox in #7057)
- Fix
unstable_renderSubtreeIntoContainer
so that context properly updates when linked to state. (@gaearon in #7125) - Improve invariant wording for void elements. (@starkch in #7066)
- Ensure no errors are thrown due to event handlers in server rendering. (@rricard in #7127)
- Fix regression resulting in
value
-less submit and reset inputs removing the browser-default text. (@zpao in #7197) - Fix regression resulting in empty
name
attribute being added to inputs when not provided. (@okonet in #7199) - Fix issue with nested server rendering. (@Aweary in #7033)
React Perf Add-on
React CSSTransitionGroup Add-on
- Fix issue resulting in spurious unknown property warnings. (@batusai513 in #7165)
React Native Renderer
- Improve error handling in cross-platform touch event handling. (@yungsters in #7143)
React
- Add error codes to production invariants, with links to the view the full error text. (@keyanzhang in #6948)
- Include component stack information in PropType validation warnings. (@spicyj in #6771)
- Include component stack information in key warnings. (@keyanzhang in #6799)
- Stop validating props at mount time, only validate at element creation. (@keyanzhang in #6823)
- New invariant providing actionable error in missing instance case. (@yungsters in #6990)
- Add
React.PropTypes.symbol
to support ES2015 Symbols as props. (@puradox in #6377) - Fix incorrect coercion of ref or key that are undefined in development (@gaearon in #6880)
- Fix a false positive when passing other element’s props to cloneElement (@ericmatthys in #6268)
React DOM
- Add warning for unknown properties on DOM elements. (@jimfb in #6800, @gm758 in #7152)
- Properly remove attributes from custom elements. (@grassator in #6748)
- Fix invalid unicode escape in attribute name regular expression. (@nbjahan in #6772)
- Add
onLoad
handling to<link>
element. (@roderickhsiao in #6815) - Add
onError
handling to<source>
element. (@wadahiro in #6941) - Handle
value
anddefaultValue
more accurately in the DOM. (@jimfb in #6406) - Fix events issue in environments with mutated
Object.prototype
. (@Weizenlol in #6886) - Fix issue where
is="null"
ended up in the DOM in Firefox. (@darobin in #6896) - Improved performance of text escaping by using escape-html. (@aickin in #6862)
- Fix issue with
dangerouslySetInnerHTML
and SVG in Internet Explorer. (@joshhunt in #6982) - Fix issue with
<textarea>
placeholders. (@jimfb in #7002) - Fix controlled vs uncontrolled detection of
<input type="radio"/>
. (@jimfb in #7003) - Improve performance of updating text content. (@trueadm in #7005)
- Ensure controlled
<select>
components behave the same on initial render as they do on updates. (@yiminghe in #5362)
React Perf Add-on
- Add
isRunning()
API. (@nfcampos in #6763) - Improve accuracy of lifecycle hook timing. (@gaearon in #6858)
- Fix internal errors when using ReactPerf with portal components. (@gaearon in #6860)
- Fix performance regression. (@spicyj in #6770)
- Add warning that ReactPerf is not enabled in production. (@sashashakun in #6884)
React CSSTransitionGroup Add-on
- Fix timing issue with
null
node. (@keyanzhang in #6958)
React Native Renderer
- Dependencies on React Native modules use CommonJS requires instead of providesModule. (@davidaurelio in #6715)
React
- Ensure we're using the latest
object-assign
, which has protection against a non-spec-compliant nativeObject.assign
. (@zpao in #6681) - Add a new warning to communicate that
props
objects passed tocreateElement
must be plain objects. (@richardscarrott in #6134) - Fix a batching bug resulting in some lifecycle methods incorrectly being called multiple times. (@spicyj in #6650)
React DOM
- Fix regression in custom elements support. (@jscissr in #6570)
- Stop incorrectly warning about using
onScroll
event handler with server rendering. (@Aweary in #6678) - Fix grammar in the controlled input warning. (@jakeboone02 in #6657)
- Fix issue preventing
<object>
nodes from being able to read<param>
nodes in IE. (@syranide in #6691) - Fix issue resulting in crash when using experimental error boundaries with server rendering. (@jimfb in #6694)
- Add additional information to the controlled input warning. (@borisyankov in #6341)
React Perf Add-on
- Completely rewritten to collect data more accurately and to be easier to maintain. (@gaearon in #6647, #6046)
React Native Renderer
- Remove some special cases for platform specific branching. (@sebmarkbage in #6660)
- Remove use of
merge
utility. (@sebmarkbage in #6634) - Renamed some modules to better indicate usage (@javache in #6643)
React
- Removed extraneous files from npm package. (@gaearon in #6388)
- Ensure
componentWillUnmount
is only called once. (@jimfb in #6613)
ReactDOM
- Fixed bug resulting in disabled buttons responding to mouse events in IE. (@nhunzaker in #6215)
- Ensure
<option>
s are correctly selected when inside<optgroup>
. (@trevorsmith in #6442) - Restore support for rendering into a shadow root. (@Wildhoney in #6462)
- Ensure nested
<body>
elements are caught when warning for invalid markup. (@keyanzhang in #6469) - Improve warning when encountering multiple elements with the same key. (@hkal in #6500)
React TestUtils Add-on
- Ensure that functional components do not have an owner. (@gaearon in #6362)
- Handle invalid arguments to
scryRenderedDOMComponentsWithClass
better. (@ipeters90 in #6529)
React Perf Add-on
React Native Renderer
- These files are now shipped inside the React npm package. They have no impact on React core or ReactDOM.
Major changes
- Initial render now uses
document.createElement
instead of generating HTML. Previously we would generate a large string of HTML and then setnode.innerHTML
. At the time, this was decided to be faster than usingdocument.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 usingcreateElement
we can make other parts of React faster. (@spicyj in #5205) data-reactid
is no longer on every node. As a result of usingdocument.createElement
, we can prime the node cache as we create DOM nodes, allowing us to skip a potential lookup (which used thedata-reactid
attribute). Root nodes will have adata-reactroot
attribute and server generated markup will still containdata-reactid
. (@spicyj in #5205)- No more extra
<span>
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<span>
s in your CSS, you will need to adjust accordingly. You can always render them explicitly in your components. (@mwiencek in #5753) - Rendering
null
now uses comment nodes. Previouslynull
would render to<noscript>
elements. We now use comment nodes. This may cause issues if making use of:nth-child
CSS selectors. While we consider this rendering behavior an implementation detail of React, it's worth noting the potential problem. ()@spicyj in #5451) - Functional components can now return
null
. We added support for defining stateless components as functions in React 0.14. However, React 0.14 still allowed you to define a class component without extendingReact.Component
or usingReact.createClass()
, so we couldn’t reliably tell if your component is a function or a class, and did not allow returningnull
from it. This issue is solved in React 15, and you can now returnnull
from any component, whether it is a class or a function. (@jimfb in #5884) - Improved SVG support. All SVG tags are now fully supported. (Uncommon SVG tags are not present on the
React.DOM
element helper, but JSX andReact.createElement
work on all tag names.) All SVG attributes that are implemented by the browsers should be supported too. If you find any attributes that we have missed, please let us know in this issue. (@zpao in #6243)
Breaking changes
- No more extra
<span>
s. React.cloneElement()
now resolvesdefaultProps
. We fixed a bug inReact.cloneElement()
that some components may rely on. If some of theprops
received bycloneElement()
areundefined
, it used to return an element withundefined
values for those props. We’re changing it to be consistent withcreateElement()
. Now anyundefined
props passed tocloneElement()
are resolved to the corresponding component’sdefaultProps
. (@truongduy134 in #5997)ReactPerf.getLastMeasurements()
is opaque. This change won’t affect applications but may break some third-party tools. We are revampingReactPerf
implementation 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 ofReactPerf.getLastMeasurements()
an opaque data structure that should not be relied upon. (@gaearon in #6286)
Removed deprecations
These deprecations were introduced nine months ago in v0.14 with a warning and are removed:
- Deprecated APIs are removed from the
React
top-level export:findDOMNode
,render
,renderToString
,renderToStaticMarkup
, andunmountComponentAtNode
. As a reminder, they are now available onReactDOM
andReactDOMServer
. (@jimfb in #5832) - Deprecated addons are removed:
batchedUpdates
andcloneWithProps
. (@jimfb in #5859, @zpao in #6016) - Deprecated component instance methods are removed:
setProps
,replaceProps
, andgetDOMNode
. (@jimfb in #5570) - Deprecated CommonJS
react/addons
entry point is removed. As a reminder, you should use separatereact-addons-*
packages instead. This only applies if you use the CommonJS builds. (@gaearon in #6285) - Passing
children
to void elements like<input>
was deprecated, and now throws an error. (@jonhester in #3372) - React-specific properties on DOM
refs
(e.g.this.refs.div.props
) were deprecated, and are removed now. (@jimfb in #5495)
New deprecations, introduced with a warning
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.
LinkedStateMixin
andvalueLink
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. (@jimfb in #6127)- Future versions of React will treat
<input value={null}>
as a request to clear the input. However, React 0.14 has been ignoringvalue={null}
. React 15 warns you on anull
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 passundefined
to make the input uncontrolled. (@antoaravinth in #5048) ReactPerf.printDOM()
was renamed toReactPerf.printOperations()
, andReactPerf.getMeasurementsSummaryMap()
was renamed toReactPerf.getWasted()
. (@gaearon in #6287)
New helpful warnings
- If you use a minified copy of the development build, React DOM kindly encourages you to use the faster production build instead. (@spicyj in #5083)
- 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: writingstyle={{'{{'}}width: '300'}}
. Unitless number values likewidth: 300
are unchanged. (@pluma in #5140) - 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 in #5940 and @koba04 in #5947)
- Elements will now warn when attempting to read
ref
andkey
from the props. (@prometheansacrifice in #5744) - React will now warn if you pass a different
props
object tosuper()
in the constructor. (@prometheansacrifice in #5346) - React will now warn if you call
setState()
insidegetChildContext()
. (@raineroviir in #6121) - React DOM now attempts to warn for mistyped event handlers on DOM elements, such as
onclick
which should beonClick
. (@ali in #5361) - React DOM now warns about
NaN
values instyle
. (@jontewks in #5811) - React DOM now warns if you specify both
value
anddefaultValue
for an input. (@mgmcdermott in #5823) - React DOM now warns if an input switches between being controlled and uncontrolled. (@TheBlasfem in #5864)
- React DOM now warns if you specify
onFocusIn
oronFocusOut
handlers as they are unnecessary in React. (@jontewks in #6296) - React now prints a descriptive error message when you pass an invalid callback as the last argument to
ReactDOM.render()
,this.setState()
, orthis.forceUpdate()
. (@conorhastings in #5193 and @gaearon in #6310) - Add-Ons:
TestUtils.Simulate()
now prints a helpful message if you attempt to use it with shallow rendering. (@conorhastings in #5358) - PropTypes:
arrayOf()
andobjectOf()
provide better error messages for invalid arguments. (@chicoxyzzy in #5390)
Notable bug fixes
- Fixed multiple small memory leaks. (@spicyj in #4983 and @victor-homyakov in #6309)
- Input events are handled more reliably in IE 10 and IE 11; spurious events no longer fire when using a placeholder. (@jquense in #4051)
- The
componentWillReceiveProps()
lifecycle method is now consistently called whencontext
changes. (@milesj in #5787) React.cloneElement()
doesn’t append slash to an existingkey
when used insideReact.Children.map()
. (@ianobermiller in #5892)- React DOM now supports the
cite
andprofile
HTML attributes. (@AprilArcus in #6094 and @saiichihashimoto in #6032) - React DOM now supports
cssFloat
,gridRow
andgridColumn
CSS properties. (@stevenvachon in #6133 and @mnordick in #4779) - React DOM now correctly handles
borderImageOutset
,borderImageWidth
,borderImageSlice
,floodOpacity
,strokeDasharray
, andstrokeMiterlimit
as unitless CSS properties. (@rofrischmann in #6210 and #6270) - React DOM now supports the
onAnimationStart
,onAnimationEnd
,onAnimationIteration
,onTransitionEnd
, andonInvalid
events. Support foronLoad
has been added toobject
elements. (@tomduncalf in #5187, @milesj in #6005, and @ara4n in #5781) - 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 in #1510) - React DOM does not mistakingly coerce
children
to strings for Web Components. (@jimfb in #5093) - React DOM now correctly normalizes SVG
<use>
events. (@edmellum in #5720) - React DOM does not throw if a
<select>
is unmounted while itsonChange
handler is executing. (@sambev in #6028) - React DOM does not throw in Windows 8 apps. (@Andrew8xx8 in #6063)
- React DOM does not throw when asynchronously unmounting a child with a
ref
. (@yiminghe in #6095) - React DOM no longer forces synchronous layout because of scroll position tracking. (@syranide in #2271)
Object.is
is used in a number of places to compare values, which leads to fewer false positives, especially involvingNaN
. In particular, this affects theshallowCompare
add-on. (@chicoxyzzy in #6132)- Add-Ons: ReactPerf no longer instruments adding or removing an event listener because they don’t really touch the DOM due to event delegation. (@antoaravinth in #5209)
### Other improvements
- React now uses
loose-envify
instead ofenvify
so it installs less transitive dependencies. (@qerub in #6303) - Shallow renderer now exposes
getMountedInstance()
. (@glenjamin in #4918) - Shallow renderer now returns the rendered output from
render()
. (@simonewebdesign in #5411) - React no longer depends on ES5 shams for
Object.create
andObject.freeze
in older environments. It still, however, requires ES5 shims in those environments. (@dgreensp in #4959) - React DOM now allows
data-
attributes with names that start with numbers. (@nLight in #5216) - React DOM adds a new
suppressContentEditableWarning
prop for components like Draft.js that intentionally managecontentEditable
children with React. (@mxstbr in #6112) - React improves the performance for
createClass()
on complex specs. (@spicyj in #5550)