[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.

Commencez par les exemples des pages de référence de useDeferredValue et useTransition et examinez comment SlowList et SlowPost affichent leur sortie. Limitez la hauteur visible de la sortie en ajoutant un défilement, tout en conservant le nombre d’éléments existant et le ralentissement intentionnel, puis vérifiez que les deux pages ne s’étendent plus excessivement.