From 6ddfd9f03a36f2974daa33e11d57a080660e5e48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?O=C4=9Fuzhan=20A=C4=9F=C4=B1r?= <90545225+oguzhanagir@users.noreply.github.com> Date: Tue, 22 Sep 2026 13:02:17 +0300 Subject: [PATCH] Revise documentation on QuickGrid and ItemsProvider Updated notes on ItemsProvider requests and breaking-change notices for QuickGrid. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../2026-09-22-blazor-net11-virtualize-anchormode-csp/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2026-09-22-blazor-net11-virtualize-anchormode-csp/POST.md b/docs/en/Community-Articles/2026-09-22-blazor-net11-virtualize-anchormode-csp/POST.md index 4358693e28..01e3229d30 100644 --- a/docs/en/Community-Articles/2026-09-22-blazor-net11-virtualize-anchormode-csp/POST.md +++ b/docs/en/Community-Articles/2026-09-22-blazor-net11-virtualize-anchormode-csp/POST.md @@ -153,7 +153,7 @@ More overscan means fewer blank moments during fast scrolling and more items to - **Bigger `ItemsProvider` requests.** With 15 items before and after the visible range, a request asks for roughly `visible + 30` items instead of `visible + 6`. - **No breaking-change notice.** The change isn't listed on the .NET 11 or ASP.NET Core 11 breaking-changes pages, so check for it yourself when you upgrade. -`QuickGrid` deliberately keeps `OverscanCount = 3`, because grid rows are heavier. See [section 13](#13-choosing-itemsize-and-overscancount) for how to choose. +`QuickGrid` deliberately keeps `OverscanCount = 3`, because grid rows are heavier. See [section 13](#choosing-itemsize-and-overscancount) for how to choose. ## The sample application: LiveStream