Re-add discrete flushing timeStamp heuristic

Re-add discrete flushing timeStamp heuristic

Re-add discrete flushing timeStamp heuristic

Author: trueadm

packages/react-dom/src/events/ReactDOMEventListener.js

@@ -130,7 +130,7 @@ function dispatchDiscreteEvent(
     // flushed for this event and we don't need to do it again.
     (eventSystemFlags & IS_LEGACY_FB_SUPPORT_MODE) === 0
   ) {
-    flushDiscreteUpdatesIfNeeded();
+    flushDiscreteUpdatesIfNeeded(nativeEvent.timeStamp);
   }
   discreteUpdates(
     dispatchEvent,

packages/react-dom/src/events/ReactDOMUpdateBatching.js

@@ -10,6 +10,8 @@ import {
   restoreStateIfNeeded,
 } from './ReactDOMControlledComponent';
 
+import {enableDeprecatedFlareAPI} from 'shared/ReactFeatureFlags';
+
 // Used as a way to call batchedUpdates when we don't have a reference to
 // the renderer. Such as when we're dispatching events or if third party
 // libraries need to call batchedUpdates. Eventually, this API will go away when
@@ -87,8 +89,27 @@ export function discreteUpdates(fn, a, b, c, d) {
   }
 }
 
-export function flushDiscreteUpdatesIfNeeded() {
-  if (!isInsideEventHandler) {
+let lastFlushedEventTimeStamp = 0;
+export function flushDiscreteUpdatesIfNeeded(timeStamp: number) {
+  // event.timeStamp isn't overly reliable due to inconsistencies in
+  // how different browsers have historically provided the time stamp.
+  // Some browsers provide high-resolution time stamps for all events,
+  // some provide low-resolution time stamps for all events. FF < 52
+  // even mixes both time stamps together. Some browsers even report
+  // negative time stamps or time stamps that are 0 (iOS9) in some cases.
+  // Given we are only comparing two time stamps with equality (!==),
+  // we are safe from the resolution differences. If the time stamp is 0
+  // we bail-out of preventing the flush, which can affect semantics,
+  // such as if an earlier flush removes or adds event listeners that
+  // are fired in the subsequent flush. However, this is the same
+  // behaviour as we had before this change, so the risks are low.
+  if (
+    !isInsideEventHandler &&
+    (!enableDeprecatedFlareAPI ||
+      timeStamp === 0 ||
+      lastFlushedEventTimeStamp !== timeStamp)
+  ) {
+    lastFlushedEventTimeStamp = timeStamp;
     flushDiscreteUpdatesImpl();
   }
 }

packages/react-dom/src/events/plugins/__tests__/ModernSimpleEventPlugin-test.js

@@ -229,16 +229,12 @@ describe('SimpleEventPlugin', function() {
   });
 
   describe('interactive events, in concurrent mode', () => {
-    beforeEach(() => {
+    // @gate experimental
+    it('flushes pending interactive work before extracting event handler', () => {
       jest.resetModules();
-
       React = require('react');
       ReactDOM = require('react-dom');
       Scheduler = require('scheduler');
-    });
-
-    // @gate experimental
-    it('flushes pending interactive work before extracting event handler', () => {
       container = document.createElement('div');
       const root = ReactDOM.unstable_createRoot(container);
       document.body.appendChild(container);