Skip to main content
Journey Uncommon Logo
JourneyUncommon
hardReactconcurrent rendering tearingSingle-choice MCQ

You wrap a state update that filters a large list in `startTransition`. A separate input's `onChange` calls `setText` outside the transition. Under concurrent rendering, why does typing stay responsive, and what is the precise relationship between the urgent `setText` update and the in-progress transition render that explains it?

function handleChange(e) { setText(e.target.value); // urgent startTransition(() => { setFilter(e.target.value); // transition (low priority) }); }