Add QuickGrid in .NET 11: Sorting and Paging That Live in the URL article - #26214
Merged
Merged
Conversation
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 75.6%, saving 498.7 KB.
|
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Several accessibility, lifecycle, and documentation claims are inaccurate or contradictory.
Review effort: Balanced
Findings: 2
Open (5)
What changed in this PR
Adds a Community Article explaining .NET 11 RC1 QuickGrid URL-based sorting and pagination.
Changes:
- Documents static SSR, multi-grid, provider, accessibility, and compatibility behavior.
- Adds a concise article summary.
| File | Description |
|---|---|
post.md |
Full QuickGrid URL-state article and samples. |
summary.md |
Article listing summary. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| - **`<a>` vs `<button>`.** Sort headers are true links now (they navigate), which is the right element for the job — screen readers announce "link", and open-in-new-tab works. Disabled paginator links carry `aria-disabled="true"` and `tabindex="-1"`. | ||
| - **`aria-sort`** shows up on the sorted `<th>` (`ascending`/`descending`, `none` elsewhere) and `scope="col"` on all headers — table semantics are intact. | ||
| - **Focus.** The template's `FocusOnNavigate` moves focus to `h1` on navigation, which keeps enhanced-nav clicks sane for keyboard users. |
| - **Go-live, not GA.** RC1 is production-supported under Microsoft's go-live license (window ends October 13, 2026 — plan to move to RC2/GA). .NET 11 is an **STS** release (support through November 9, 2028); .NET 10 remains **LTS** (November 14, 2028). The support windows end in the same month, so choose on features and risk, not longevity. | ||
| - **Duplicate provider calls on `?page=` requests** ([observed above](#server-side-paging-with-griditemsprovider)) — budget for it or use `Items` for small tables. See also [dotnet/aspnetcore#69381](https://github.com/dotnet/aspnetcore/issues/69381). | ||
| - **Markup breaking change.** `button.col-title` → `a.col-title` and paginator `button` → `a`. CSS selectors and Playwright/Selenium locators targeting `button` need updating; `aria-disabled` replaces `:disabled` for the disabled paginator state. | ||
| - **`Paginator.OnParametersSet` → `OnParametersSetAsync`.** Binary-compatible but behaviorally breaking for `Paginator` subclasses that overrode the sync method — they silently stop being called. |
|
|
||
| - **Static SSR works.** Sorting and paging are functional on pages with no interactivity at all — headers and the paginator are `<a>` links carrying `sort`, `direction`, and `page` query parameters. | ||
| - **The URL is the state store.** Refresh, Back/Forward, bookmarks, and "copy link" all preserve the grid state because the state is the address. | ||
| - **Your own parameters coexist.** A `[SupplyParameterFromQuery]` filter like `?country=Germany` is preserved inside QuickGrid's generated links, and vice versa. |
|
|
||
| ## The sample app | ||
|
|
||
| The sample is a Blazor Web App with **no interactivity on its pages** — the scenario that was impossible before .NET 11: |
| string Sort, Direction, Page // settable | ||
| ``` | ||
|
|
||
| > **Docs lag the RC1 rename.** The QuickGrid docs page and several preview-era blog posts still show `QueryParameterNamePrefix` and `?order=`. On RC1 that parameter doesn't exist and `order` is ignored — use `QueryParameterNameOptions` and `direction`. |
Member
|
@salihozkara can you check once copilot findings? Later I'll review |
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 8.2%, saving 10.0 KB.
1 image did not require optimisation. |
Contributor
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 7%, saving 5.5 KB.
3 images did not require optimisation. |
enisn
approved these changes
Sep 29, 2026
enisn
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.