Just rechecked the issue hiro mentioned: the start value on the devtools, and perhaps other places: We replace the startValue on the compositor, but the keyframe doesn't know this update (or say, the new start value) on the main thread. This may cause some issues on the main thread. So perhaps we still have to do replacement on the main thread, and use IPC to retrieve the last AnimationValue if possible.
Bug 1626165 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Just rechecked the issue hiro mentioned: the start value on the devtools, and perhaps other places (e.g. sync with mouse event?): We replace the startValue on the compositor, but the keyframe doesn't know this update (or say, the new start value) on the main thread. This may cause some issues on the main thread. So perhaps we still have to do replacement on the main thread, and use IPC to retrieve the last AnimationValue if possible.
Just rechecked the issue hiro mentioned: the start value on the devtools, and perhaps other places (e.g. sync with mouse event?): We replace the startValue on the compositor, but the keyframe doesn't know the new start value on the main thread. This may cause some issues on the main thread. So perhaps we still have to do replacement on the main thread, and use IPC to retrieve the last AnimationValue if possible.
Just rechecked the issue hiro mentioned: the start value on the devtools, and perhaps other places (e.g. sync with mouse event?): We replace the startValue on the compositor, but the keyframe doesn't know the new start value on the main thread. This may cause some issues on the main thread. So perhaps we still have to do the replacement on the main thread, and use IPC to retrieve the last AnimationValue if possible.