You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Suggestion]: Cap the height of the artificially-slow example output (useDeferredValue / useTransition) #8486
When you view the example's rendered output in full, the SlowList/SlowPost demos expand into hundreds of identical rows, which is more than anyone needs to scroll through. The output height should be capped (e.g. max-height + scroll) while keeping the item counts that create the intentional slowdown.
The point of these demos is felt within the first few rows — you just need to see the list "lag behind" the input. But the rendered output shows the full list, so viewing it expands the example to hundreds of identical "Text:" rows and pushes the rest of the docs far down. The number of rows differs across pages (250 / 500 / 50), so the problem shows up unevenly.
Thanks for offering! Actually I opened this issue intending to work on it myself — I'd like to take this one. I'll open a PR with the max-height + scroll approach shortly. Hope that's okay!
Activity
lee-eojin commentedon Jun 23, 2026
Thanks for offering! Actually I opened this issue intending to work on it myself — I'd like to take this one. I'll open a PR with the max-height + scroll approach shortly. Hope that's okay!