Currently the simple event plugin defines a priority for the event but not all events go through the SimpleEventPlugin. That's just one of several EventPlugins. The remaining ones now get the wrong priority associated with them. 

E.g. I think all of these should be discrete:

change
compositionend
compositionstart
compositionupdate
selectionchange
textinput

These show up too but I don't know if they're even bridged.

dblclick
pointerenter
pointerleave

Flare defines its own priorities.
getNearestMountedFiber,
  getContainerFromFiber,
  getSuspenseInstanceFromFiber,
} from 'react-reconciler/src/ReactFiberTreeReflection';
import {HostRoot, SuspenseComponent} from 'react-reconciler/src/ReactWorkTags';
import {
  type EventSystemFlags,
  IS_CAPTURE_PHASE,
  IS_LEGACY_FB_SUPPORT_MODE,
} from './EventSystemFlags';
import getEventTarget from './getEventTarget';
import {getClosestInstanceFromNode} from '../client/ReactDOMComponentTree';
import {
  enableLegacyFBSupport,
  enableNewReconciler,
} from 'shared/ReactFeatureFlags';
import {dispatchEventForPluginEventSystem} from './DOMPluginEventSystem';
import {
  flushDiscreteUpdatesIfNeeded,
  discreteUpdates,
} from './ReactDOMUpdateBatching';
import {
  InputContinuousLanePriority as InputContinuousLanePriority_old,
  getCurrentUpdateLanePriority as getCurrentUpdateLanePriority_old,
  setCurrentUpdateLanePriority as setCurrentUpdateLanePriority_old,
} from 'react-reconciler/src/ReactFiberLane.old';
import {
  InputContinuousLanePriority as InputContinuousLanePriority_new,
  getCurrentUpdateLanePriority as getCurrentUpdateLanePriority_new,
  setCurrentUpdateLanePriority as setCurrentUpdateLanePriority_new,