Description: Investigate the interaction between motion lifecycle and React rendering. When a motion finishes, when does React know? Are there races between motion completion and state updates that depend on it? How do controlled vs. uncontrolled motion components handle this? Audit the patterns used in the 6 motion components, presence components, and choreography components. Produce a findings report. Land small fixes (e.g., missing completion callbacks, off-by-one timing issues) in scope. Defer larger redesigns.
Why it matters: "The motion finished but the parent didn't re-render" is a classic source of subtle bugs in motion systems. Choreography (CHOR-02 work) will stress this — better to audit before that signal arrives so the UXE can recognize it.
- Difficulty: Medium-Hard (timing/race issues are subtle)
- Sequencing: M3 W10
- Tags:
partner-pickup
- Cross-ref: Findings may feed Group 5 API decisions (specifically around lifecycle/completion callbacks)
Description: Investigate the interaction between motion lifecycle and React rendering. When a motion finishes, when does React know? Are there races between motion completion and state updates that depend on it? How do controlled vs. uncontrolled motion components handle this? Audit the patterns used in the 6 motion components, presence components, and choreography components. Produce a findings report. Land small fixes (e.g., missing completion callbacks, off-by-one timing issues) in scope. Defer larger redesigns.
Why it matters: "The motion finished but the parent didn't re-render" is a classic source of subtle bugs in motion systems. Choreography (CHOR-02 work) will stress this — better to audit before that signal arrives so the UXE can recognize it.
partner-pickup