Description
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Right now the cursor: pointer automatically gets applied to mat-sort-header-container. Why not use mat-sort-header instead? Checking the example e.g. in the table (https://material.angular.io/components/sort/overview#using-sort-with-the-mat-table) there is a clickable area with no cursor indication. I think the cursor should be applied to the element implementing the click handler.
Reproduction
Just check your example (https://material.angular.io/components/sort/overview#using-sort-with-the-mat-table) and click in an area without cursor.
Expected Behavior
Just the area with cursor should handle the click.
Actual Behavior
No cursor, no handler.
Environment
Angular CLI: 19.1.9
Node: 22.11.0
Package Manager: pnpm 10.6.2
OS: win32 x64
Angular: 19.1.8
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker
Package Version
@angular-devkit/architect 0.1901.9 (cli-only)
@angular-devkit/build-angular 19.1.9
@angular-devkit/core 19.1.9 (cli-only)
@angular-devkit/schematics 19.1.9 (cli-only)
@angular/cdk 19.1.5
@angular/cli 19.1.9
@angular/material 19.1.5
@angular/material-luxon-adapter 19.1.5
@schematics/angular 19.1.9 (cli-only)
rxjs 7.8.2
typescript 5.7.3
zone.js 0.15.0