Rubén NorteandGitHub 5e653d49a0 [RN] Fix timeStamp property of SyntheticEvent in React Native (#35912) ...

## Summary

This fixes the semantics of the `timeStamp` property of events in React
Native.

Currently, most events just assign `Date.now()` (at the time of creating
the event object in JavaScript) as the `timeStamp` property. This is a
divergence with Web and most native platforms, that use a monotonic
timestamp for the value (on Web, the same timestamp provided by
`performance.now()`).

Additionally, many native events specify a timestamp in the event data
object as `timestamp` and gets ignored by the logic in JS as it only
looks at properties named `timeStamp` specifically (camel case).

This PR fixes both issues by:
1. Using `performance.now()` instead of `Date.now()` by default (if
available).
2. Checking for a `timestamp` property before falling back to the
default (apart from `timeStamp`).

## How did you test this change?

Added unit tests for verify the new behavior.

2026-02-26 15:51:07 +00:00

..

src

[RN] Fix timeStamp property of SyntheticEvent in React Native (#35912)

2026-02-26 15:51:07 +00:00

fabric.js

ESLint upgrade to use hermes-eslint (#25915)

2022-12-20 14:27:01 -05:00

index.js

[rn] delete the legacy renderers from the sync (#34946)

2025-10-27 17:38:56 -04:00

package.json

Bump next prerelease version numbers (#34674)

2025-10-02 00:31:55 +02:00