Joshua Gross 11990c5a08 NativeAnimatedModule: ensure that all operations execute in order when switching between Fabric and non-Fabric screens ...

Summary:
There are potential race conditions in the old implementation that could result in operations being executed out-of-order when the user transitions between Fabric/non-Fabric screens.

Specifically, if the non-Fabric path queues up a batch of operations to execute on the next UI tick, it is possible that Fabric lifecycle events fire /before/ that next UI tick and synchronously execute a batch of animation operations on the UI thread, before their predecessors have executed.

Changelog: [Internal]

Reviewed By: mdvacca

Differential Revision: D22564633

fbshipit-source-id: 91c24547d5a682e61fc0c433302667330349a5f1

2020-07-15 23:14:14 -07:00

..

debug

use xplat BUCK attribution

2020-05-15 21:55:52 -07:00

fbreact/specs

Move CameraRoll Android files to FB Internal

2020-07-09 06:10:42 -07:00

hermes

use xplat BUCK attribution

2020-05-15 21:55:52 -07:00

perftest

Tidy up license headers [2/n]

2019-10-16 10:06:34 -07:00

proguard/annotations

Tidy up license headers [2/n]

2019-10-16 10:06:34 -07:00

react

NativeAnimatedModule: ensure that all operations execute in order when switching between Fabric and non-Fabric screens

2020-07-15 23:14:14 -07:00

systrace

Tidy up license headers [2/n]

2019-10-16 10:06:34 -07:00

yoga

fix typo as there is no file called YGJNI.cpp (#990)

2020-04-17 05:46:14 -07:00

BUCK

Migrate to FBJNI (#27729)

2020-01-21 02:32:50 -08:00