[rubennorte]

Summary:
#59896 made ReactNativeElement unconditionally extend EventTarget, which imports the AbortSignal type, pulling AbortSignal.d.ts into the generated types checked by yarn test-generated-typescript. The internal abortSignal(reason = ..., signal) helper declares a defaulted parameter before a required one, which flow-api-translator emits as abortSignal(reason?: unknown | void, signal: AbortSignal) and tsc rejects with TS1016.

Reorder the parameters to abortSignal(signal, reason = ...) and update both internal callers. The public API snapshot is unchanged.

Changelog: [Internal]

Test Plan:

• yarn build-types --skip-snapshot && yarn test-generated-typescript: fails with TS1016 before, passes after
• yarn build-types --validate: API snapshot is up to date
• yarn eslint --max-warnings 0 packages/react-native/src/private/webapis/dom/abort-api/

[YevheniiKotyrlo]

#59896 also leaves Fantom red on main: EventTargetDispatching-itest.js fails 16 cases in its enableImperativeEvents ✅ variant, where a listener added with addEventListener receives no dispatched event (expect(handler).toHaveBeenCalledTimes(1) at line 509 gets 0 calls). Every Test All run from 9f40f16 on fails all three Fantom attempts on them, such as this one on b13546b8ce.

[rubennorte]

#59896 also leaves Fantom red on main: EventTargetDispatching-itest.js fails 16 cases in its enableImperativeEvents ✅ variant, where a listener added with addEventListener receives no dispatched event (expect(handler).toHaveBeenCalledTimes(1) at line 509 gets 0 calls). Every Test All run from 9f40f16 on fails all three Fantom attempts on them, such as this one on b13546b8ce.

That's an unrelated breakage. I'll fix both in #59911.