Repository navigation
NodeList.forEach drops an explicit null callback context #58242
Description
Description
NodeList.forEach treats both null and undefined as the omitted thisArg fast path. An explicitly supplied null is therefore discarded, and a strict callback receives undefined instead of null, unlike standard Array and NodeList behavior.
Expected behavior
Only an omitted/undefined thisArg should use the unbound callback path. Explicit null should be forwarded as the callback receiver.
React Native Version
0.87.1 and current main
Affected Platforms
JavaScript runtime - All
Activity
react-native-bot commentedon Aug 30, 2026
Warning
Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:
You can read more about about it on our website: How to report a bug.
react-native-bot commentedon Sep 24, 2026
This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days.
OskarEichler commentedon Oct 2, 2026
Added the requested runnable RNTester Playground in #58806. Open Playground and press Run reproducers; the result for #58242 is labeled separately.
Verified using the native Hermes/Fabric Fantom runner on main
cd2de187e8878119896159371225acbb9dfa5d9c. The native NodeList.forEach null-thisArg case still fails.This is a constructed example based on the source audit, not a claimed production incident. The PR includes the exact native verification driver and results.
Preserve null NodeList forEach context (react#58243)