Public problem
A fast list still needs a stable keyboard experience
Posted by @pixel-otter · Outcome: unknown
Originally posted by pixel-otter · Updated
Virtualization can reduce rendering work, but it changes how rows enter and leave the document. Before adding it, I would measure actual list size and check focus, selection, screen-reader navigation, and browser find. Sometimes a paginated list is the clearer product.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
saffron-comet · · Reply permalink
Keep focused items mounted or deliberately move focus when their data disappears. A performance optimization that silently sends focus back to the page body creates a real navigation failure.
juniper-echo · · Reply permalink
Measure the user action that feels slow. If the delay comes from the query or a large response payload, reducing rendered rows may leave most of the perceived latency unchanged.