Fix InitialItemIndex viewport underfill for small items in big container

[ilonatommy]

Fixes #67933

Problem

Loading a Virtualize (or QuickGrid) at a small InitialItemIndex e.g. 10 rendered only a few rows below the target and left a blank gap at the bottom of the viewport, with no items and no placeholders. The gap only filled once the user manually scrolled. Best visible in bigger containers with smaller than average items.

Example: a 300px container with fixed 50px rows fits 6 rows. InitialItemIndex=10 rendered only items 10–13, leaving room for 14 and 15 empty.

Root cause

InitialItemIndex aligns the target row to the top of the viewport.

On a fresh load, before any spacer-observer measurement has arrived, MoveWindowToContain only has a minimal seed capacity (OverscanCount * 2 + 1). It still reserved OverscanCount rows before the target. Because the target is top-aligned, those leading rows land off-screen (above). The small seed window no longer has enough rows to cover the area below the target. The shorter the final rendered items and the bigger the viewport, the more the issue is visible. From this reason regression tests are growing the container 300px->900px.

• QuickGrid (default OverscanCount = 3) -> seed of 7 rows, 3 wasted above -> underfills.
• Pure  Virtualize  (OverscanCount = 15) -> seed of 31 rows, big enough to mask the issue in most cases.

The window would only correct itself via a spacer-observer callback, which is suppressed during a programmatic scroll.

Fix

The goal was to make the InitialIndexItem logic more similar to 0-th item loading logic that never has issues with filling in the viewport because it doesn't suppress callbacks. To achieve it, we release OnSpacerBeforeVisible callbacks until the viewport is filled so that C# fills the rows below the target, covering the whole viewport immediately, without user manual scrolls. It basically acts like the user scroll but keeping the scrollTop pinned to the target position.

[Copilot]

Pull request overview

This PR fixes a Blazor Virtualize/QuickGrid startup issue where small InitialItemIndex values could leave the viewport bottom underfilled until the user scrolls. It does this by deferring “leading overscan” (items reserved above the target) until the component has received its first spacer/measurement feedback, and adds E2E coverage to prevent regressions.

Changes:

• Add a _hasSpacerFeedback flag to detect when initial spacer observer feedback has occurred and use it to avoid reserving pre-target overscan during the initial unmeasured window seed.
• Mark spacer feedback as received when OnBeforeSpacerVisible/OnAfterSpacerVisible run, restoring the normal overscan-before-target behavior after measurement.
• Add E2E tests asserting that both QuickGrid and Virtualize fill the viewport for small InitialItemIndex values (including a small overscan scenario), plus minor test-asset updates to support the scenario.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
src/Components/Web/src/Virtualization/Virtualize.cs	Defers leading overscan until spacer feedback exists to prevent initial viewport underfill.
src/Components/test/testassets/BasicTestApp/VirtualizationAnchorMode.razor	Adds a UI toggle to set a small overscan to reproduce/validate the scenario.
src/Components/test/testassets/BasicTestApp/QuickGridTest/QuickGridScrollComponent.razor	Adjusts rendered item styling in the scroll/initial-index test component used by E2E coverage.
src/Components/test/E2ETest/Tests/VirtualizationTest.cs	Adds E2E assertions ensuring initial-index loads cover the viewport bottom with real items for both QuickGrid and Virtualize.