IssueTracker

Coroutine scopes derived from a composition using the rememberCoroutineScope() and launchInComposition APIs should have the Recomposer's MonotonicFrameClock in their coroutineContexts. The absence of this causes jank in animations performed using the withFrameNanos API family as ordering of frame operations with regard to the recomposer loop are not guaranteed. This bug was masked by the CompositionCoroutineScope receiver used by launchInComposition implementing the frame clock interface and providing the correct one through that side channel.

Install the correct frame clock into the coroutineContext and remove CompositionCoroutineScope's interface implementation of MonotonicFrameClock.