[Bug]:Possible wrong descrption for useDeferredValue

Summary

The doucmention describe the wrong behaviour for useDeferredValue

Page

https://react.dev/reference/react/Suspense

Details

The documentation says:

The query will update immediately, so the input will display the new value. However, the deferredQuery will keep its previous value until the data has loaded

From my test, deferredQuery also updates immediately rather than waiting for the data to be loaded here is the link https://codesandbox.io/p/sandbox/react-dev-forked-kxfktt

useDeferredValue consistently lags query with around 4 or 5 ms

Think about it, if deferredQuery updates after SearchResults is ready, how SearchResults receive the latest data at the first place?

The real reason we can see opacity: 0.2 for several seconds is that the new content is not rendered yet; rather than

the deferredQuery will keep its previous value until the data has loaded

If my understanding is correct, I should say the documentation is misleading, especially for the newbies

Leggi il passaggio su useDeferredValue su https://react.dev/reference/react/Suspense e riproduci il comportamento nel CodeSandbox collegato. Confronta la formulazione relativa a deferredQuery con la tempistica osservata, quindi aggiorna la documentazione in modo che spieghi accuratamente quando cambia il valore e cosa indica l’opacità.