See associated pull request for more information.

(cherry picked from commit 0d26886)

Adds a function that provides more granular information about why animations are disabled.

(cherry picked from commit d1083d7)

…pping them

Reworks the progress bar to slow down its animations, instead of fully stopping them when `prefers-reduced-motion` is enabled. Stopping the animations completely appears to be confusing for users.

(cherry picked from commit 9507900)

… stopping them

Reworks the progress spinner to slow down its animations, instead of fully stopping them when `prefers-reduced-motion` is enabled. Stopping the animations completely appears to be confusing for users.

(cherry picked from commit 062c5eb)

…#31316)

* fix(cdk/scrolling): Prevent virtual scroll 'flickering' with zoneless

This commit reworks the change detection coalescing to use signal and effects, which ensures the transform and the afterNextRender are applied within the same application tick without any awkward workarounds or fiddling with being inside or outside the zone

* fixup! fix(cdk/scrolling): Prevent virtual scroll 'flickering' with zoneless

* fixup! fix(cdk/scrolling): Prevent virtual scroll 'flickering' with zoneless

(cherry picked from commit cea7989)

Co-authored-by: lukas <[email protected]>
(cherry picked from commit 27dae25)

…n M3 (#31565)

There were two issues preventing the active styles for the datepicker toggle from showing up in M3:
1. In M2 the inner button had a `color: inherit` which allowed it to inherit the color from the toggle, however in M3 the button has a specific color.
2. The M3 tokens for the datepicker weren't setting the right color.

(cherry picked from commit 5bd42ea)

…#31572)

If the user hits the end of the calendar (e.g. when a min/max date is set), we disable the calendar button which causes focus to be returned to the `body`.

These changes use `disabledInteractive` on the buttons so that focus stays on the button.

(cherry picked from commit e8b28fa)

See associated pull request for more information.

(cherry picked from commit 5d44cd7)

…1568)

This is something that showed up in some internal tests a while ago. Because we set `mat-focused` through a host binding while `mdc-text-field--focused` is set through direct DOM manipulation, nothing guarantees that they'll be in sync and in some internal tests they aren't.

These changes sync both of them up from the same place.

(cherry picked from commit 8eae162)

(cherry picked from commit 307ad0c)

(cherry picked from commit 3de2b96)

Fixes that the lock file in the patch branch was out of sync.