onChange doesn't fire if input re-renders due to a setState() in a non-React capture phase listener

Extracting from https://github.com/facebook/react/issues/12643. This issue has always been in React. I can reproduce it up to React 0.11. However **it's probably extremely rare in practice and isn't worth fixing**. I'm just filing this for posterity. Here is a minimal example. ```js class App extends React.Component { state = {value: ''} handleChange = (e) => { this.setState({ value: e.target.value }); } componentDidMount() { document.addEventListener( "input", () => { // COMMENT OUT THIS LINE TO FIX: this.setState({}); }, true ); } render() { return ( <div> <input value={this.state.value} onChange={this.handleChange} /> </div> ); } } ReactDOM.render(<App />, document.getElementById("container")); ``` Typing doesn't work — unless I comment out that `setState` call in the capture phase listener. Say the input is empty and we're typing `a`. What happens here is that `setState({})` in the capture phase non-React listener runs first. When re-rendering due to that first empty `setState({})`, input props still contain the old value (`""`) while the DOM node's value is new (`"a"`). They're not equal, so we'll set the DOM node value to `""` (according to the props) and remember `""` as the current value. <img width="549" alt="screen shot 2018-08-17 at 1 08 42 am" src="https://user-images.githubusercontent.com/810438/44241204-4b0e0880-a1ba-11e8-847d-bf9ca43eb954.png"> Then, `ChangeEventPlugin` tries to decide whether to emit a change event. It asks the tracker whether the value has changed. The tracker compares the presumably "new" `node.value` (it's `""` — we've just set it earlier!) with the `lastValue` it has stored (also `""` — and also just updated). No changes! <img width="505" alt="screen shot 2018-08-17 at 1 10 59 am" src="https://user-images.githubusercontent.com/810438/44241293-e0110180-a1ba-11e8-9c5a-b0d808f745cd.png"> Our `"a"` updat…