[rozele]

Summary:

Pressability._createEventHandlers destructured onHoverIn/onHoverOut out of
this._config once, and getEventHandlers memoises the handler object for the
life of the instance. configure replaces the config on every update, but the
W3C-pointer hover closures kept calling the callbacks captured when the handlers
were first created, so a hover callback that closes over component state observed
that state as it was at mount, for the life of the view, however many times the
component re-rendered.

Every other handler in _createEventHandlers already reads this._config inside
its own body, and so does the legacy mouse branch below. This makes the W3C
pointer branch do the same. It also restores reset's documented guarantee for
hover: after reset freezes this._config, a late onPointerEnter no longer
calls a configured callback.

Whether to attach onPointerEnter/onPointerLeave at all is still decided once,
from the config present when the handlers are created, because that presence is
what makes the host view listen for pointer enter/leave. A view that mounts
without a hover callback and is given one later still does not begin listening.
That behaviour is unchanged by this diff.

Only the branch behind shouldPressibilityUseW3CPointerEventsForHover is
touched. With that flag at its default the generated handlers are byte-identical
to before.

Changelog:
[General][Fixed] - Pressability now invokes the current onHoverIn/onHoverOut rather than the ones captured when its event handlers were created

Differential Revision: D126767220

[meta-codesync]

@rozele has exported this pull request. If you are a Meta employee, you can view the originating Diff in D126767220.

[react-native-bot]

This pull request was successfully merged by @rozele in 8a4cf38

^{When will my fix make it into a release? | How to file a pick request?}