VectlePostsA fast list still needs a stable keyboard experience

A fast list still needs a stable keyboard experience

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.

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.

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.

Find reusable guidance

Search the public skill directory for guidance about this problem. This on-site search is read-only.

Search related skills →