[Blazor] Add OnRowClick EventCallback to QuickGrid

[javiercn]

Summary

This PR adds a new OnRowClick parameter to the QuickGrid component, allowing users to handle row click events. This addresses a common scenario where developers need to respond to user clicks on grid rows.

Fixes #44899

Changes

• Added OnRowClick parameter of type EventCallback<TGridItem> to QuickGrid
• When the delegate is set:
  • Row elements receive a row-clickable CSS class
  • A cursor: pointer style is applied via scoped CSS
  • Clicking the row invokes the callback with the clicked item
• Added E2E tests to verify the callback is triggered and cursor style is applied

Usage Example

<QuickGrid Items="@people" OnRowClick="HandleRowClick">
    <PropertyColumn Property="@(p => p.Name)" />
</QuickGrid>

@code {
    void HandleRowClick(Person person)
    {
        // Handle the row click
        Console.WriteLine($"Clicked: {person.Name}");
    }
}

Files Changed

File	Description
QuickGrid.razor	Added if/else in RenderRow to apply click handler and CSS class
QuickGrid.razor.cs	Added OnRowClick parameter with XML docs
QuickGrid.razor.css	Added .row-clickable CSS class with cursor:pointer
PublicAPI.Unshipped.txt	Documented new public API
SampleQuickGridComponent.razor	Updated test component with OnRowClick handler
QuickGridTest.cs	Added E2E tests for OnRowClick behavior

[Copilot]

Pull request overview

This PR adds an OnRowClick EventCallback parameter to the QuickGrid component, enabling developers to handle row click events. The implementation conditionally applies the row-clickable CSS class and click handler when the callback is set, with accompanying E2E tests to verify functionality.

Key Changes:

• Added OnRowClick EventCallback parameter to QuickGrid
• Implemented conditional rendering in RenderRow to attach click handlers and apply styling when the callback is set
• Added CSS styling (cursor: pointer) for clickable rows via the row-clickable class

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
QuickGrid.razor	Modified RenderRow method to conditionally apply click handlers and row-clickable class based on OnRowClick.HasDelegate
QuickGrid.razor.cs	Added OnRowClick parameter with XML documentation
QuickGrid.razor.css	Added .row-clickable CSS class with cursor: pointer styling
PublicAPI.Unshipped.txt	Documented the new public API getter/setter for OnRowClick
SampleQuickGridComponent.razor	Updated test component to include row click handling with state tracking
QuickGridTest.cs	Added E2E tests verifying callback invocation and cursor styling
Agents.md	New documentation file (unrelated to this PR's purpose)

[javiercn]

@copilot fix the following test

Microsoft.AspNetCore.Components.E2ETests.Tests.QuickGridTest.RowClassApplied

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "highlight"
Actual:   "row-clickable highlight"
           ↑ (pos 0)

Update to match the expectations as needed.

Also implement the suggestion from

The if/else block contains significant code duplication. The only differences between the two branches are the @OnClick handler and the row-clickable class. Consider consolidating this logic to avoid duplication:

You can remove the commit about Agents.md from this change too.

Anything else, leave it be.

[Copilot]

@javiercn I've opened a new pull request, #64606, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@javiercn I've opened a new pull request, #64621, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@javiercn I've opened a new pull request, #64628, to work on those changes. Once the pull request is ready, I'll request review from you.

[ilonatommy]

How does the row click behave when it comes to propagation? Will a click on the element bubble up to its ancestor DOM element? Do we have to support stopPropagation?

[javiercn]

Blazor uses event delegation for handling events. All events bubble up to the root where the handler intercepts them and then dispatches to the appropriate Blazor code. We normally don't stop event propagation unless we have good reasons to.

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-10.0#stop-event-propagation