(nativeEvent)
| 3935 | } |
| 3936 | |
| 3937 | function manualDispatchChangeEvent(nativeEvent) { |
| 3938 | var event = createAndAccumulateChangeEvent(activeElementInst, nativeEvent, getEventTarget(nativeEvent)); |
| 3939 | |
| 3940 | // If change and propertychange bubbled, we'd just bind to it like all the |
| 3941 | // other events and have it go through ReactBrowserEventEmitter. Since it |
| 3942 | // doesn't, we manually listen for the events and so we have to enqueue and |
| 3943 | // process the abstract event manually. |
| 3944 | // |
| 3945 | // Batching is necessary here in order to ensure that all event handlers run |
| 3946 | // before the next rerender (including event handlers attached to ancestor |
| 3947 | // elements instead of directly on the input). Without this, controlled |
| 3948 | // components don't work properly in conjunction with event bubbling because |
| 3949 | // the component is rerendered and the value reverted before all the event |
| 3950 | // handlers can run. See https://github.com/facebook/react/issues/708. |
| 3951 | batchedUpdates(runEventInBatch, event); |
| 3952 | } |
| 3953 | |
| 3954 | function runEventInBatch(event) { |
| 3955 | runEventsInBatch(event, false); |
no test coverage detected