Blazor Preview 5 patch examples

[guardrex]

Addresses #37206

Sorry for the delay, Wade! Great catch on those gremlins 😈!

Please go ahead and merge this if it looks good to you.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/components/quickgrid.md	aspnetcore/blazor/components/quickgrid

[Copilot]

Pull request overview

Updates the Blazor QuickGrid documentation samples for .NET 11 Preview 5 by tightening query-string handling and fixing navigation usage in the paging/details examples.

Changes:

• Update the Details.razor sample to treat Id/Page as nullable query parameters and to generate a “Back to List” link that works when page is missing.
• Update the SciFiCharacters.razor sample to inject NavigationManager and use the injected instance for navigation.
• Update the < aspnetcore-11.0 sample to make the Page query parameter nullable.

Comments suppressed due to low confidence (1)

aspnetcore/blazor/components/quickgrid.md:525

• Page is treated as a 1-based page number, but the code only checks HasValue. If a user supplies ?page=0 (or a negative value), Page.Value - 1 becomes negative and can cause SetCurrentPageIndexAsync to throw. Guard for Page > 0 (or clamp to 1) before subtracting.

    private int? Page { get; set; }

    protected override async Task OnInitializedAsync()
    {
        if (Page.HasValue)

[guardrex]

Hold a sec ... I like Copilot's remark ...

Page is treated as a 1-based page number, but the code only checks HasValue. If a user supplies ?page=0 (or a negative value), Page.Value - 1 becomes negative and can cause SetCurrentPageIndexAsync to throw. Guard for Page > 0 (or clamp to 1) before subtracting.

UPDATE: Done! 👍

[wadepickett]

...reviewing....

[wadepickett]

Suggested change

	ms.date: 06/11/2026

[wadepickett]

Looks great. Approved. I reset the ms.date, becuase I could.