Uh oh!
There was an error while loading. Please reload this page.
[RN] Move new event dispatching pipeline to RN - #36266
Conversation
Comparing: 5682442...3902c46 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show
|
da016ec to
3902c46Comparejavache
commented
Apr 14, 2026
This logic deals with |
Uh oh!
There was an error while loading. Please reload this page.
rubennorte
commented
Apr 14, 2026
The implementation in RN has changed to not use fibers and traverse via public instances instead, as we do for regular event dispatching. |
## Summary We found a bug in the logic in #36253 and we realized it's very inconvenient to iterate on the implementation when it's in this repository, as we're forced to then synchronize it to RN to test changes. This moves the entire implementation to RN for simplicity and also to simplify some clean ups in the future (like removing `top` prefixes from native event types). ## How did you test this change? The changes are gated. Will test e2e in RN. DiffTrain build for [0418c8a](0418c8a)
## Summary We found a bug in the logic in react#36253 and we realized it's very inconvenient to iterate on the implementation when it's in this repository, as we're forced to then synchronize it to RN to test changes. This moves the entire implementation to RN for simplicity and also to simplify some clean ups in the future (like removing `top` prefixes from native event types). ## How did you test this change? The changes are gated. Will test e2e in RN. DiffTrain build for [0418c8a](react@0418c8a)
## Summary We found a bug in the logic in react#36253 and we realized it's very inconvenient to iterate on the implementation when it's in this repository, as we're forced to then synchronize it to RN to test changes. This moves the entire implementation to RN for simplicity and also to simplify some clean ups in the future (like removing `top` prefixes from native event types). ## How did you test this change? The changes are gated. Will test e2e in RN. DiffTrain build for [0418c8a](react@0418c8a)
[diff react/react@fef12a01...da9325b5](react/react@fef12a0...da9325b) <details> <summary>React upstream changes</summary> - react/react#35962 - react/react#35961 - react/react#36277 - react/react#36297 - react/react#36292 - react/react#36291 - react/react#36196 - react/react#36246 - react/react#36287 - react/react#36285 - react/react#36274 - react/react#36266 - react/react#36253 </details>
…#92945) [diff react/react@fef12a01...da9325b5](react/react@fef12a0...da9325b) <details> <summary>React upstream changes</summary> - react/react#35962 - react/react#35961 - react/react#36277 - react/react#36297 - react/react#36292 - react/react#36291 - react/react#36196 - react/react#36246 - react/react#36287 - react/react#36285 - react/react#36274 - react/react#36266 - react/react#36253 </details>
Summary
We found a bug in the logic in #36253 and we realized it's very inconvenient to iterate on the implementation when it's in this repository, as we're forced to then synchronize it to RN to test changes.
This moves the entire implementation to RN for simplicity and also to simplify some clean ups in the future (like removing
topprefixes from native event types).How did you test this change?
The changes are gated. Will test e2e in RN.