[Suggestion]: Cap the height of the artificially-slow example output (useDeferredValue / useTransition)

Summary

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.

Page

https://react.dev/reference/react/useDeferredValue
https://react.dev/reference/react/useTransition

Details

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.

Inizia con gli esempi nelle pagine di riferimento di useDeferredValue e useTransition e analizza il modo in cui SlowList e SlowPost eseguono il rendering del loro output. Limita l’altezza visibile dell’output con lo scorrimento, mantenendo invariati i conteggi degli elementi esistenti e il rallentamento intenzionale, quindi verifica che entrambe le pagine non si espandano più eccessivamente.