[Fluent] Adding RecognizesAccessKey=True in remaining Fluent control styles

[dipeshmsft]

Fixes #10928

Description

Adds RecognizesAccessKey property to RepeatButton, ToggleButton and Expander controls.

Customer Impact

Customers using Access keys to navigate in the application will get the correct behavior.

Regression

No

Testing

Local app testing

Risk

Minimal

Microsoft Reviewers: Open in CodeFlow

[Copilot]

Pull Request Overview

This pull request addresses issue #10928 by ensuring that controls correctly support access key behavior. The key changes are:

• Adding RecognizesAccessKey="True" to RepeatButton and ToggleButton templates.
• Updating styles in various themes (Fluent, Fluent.Light, Fluent.HC, and Fluent.Dark) and control-specific XAML files.
• Altering the Expander control template, although its changes seem inconsistent with the stated goal.

Reviewed Changes

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

Show a summary per file

File	Description
Fluent.xaml	Updates RepeatButton and ToggleButton templates; Expander template removes RecognizesAccessKey attribute.
Fluent.Light.xaml	Similar updates for RepeatButton/ToggleButton; Expander template change removes the property.
Fluent.HC.xaml	Adds RecognizesAccessKey for some controls while removing it for Expander.
Fluent.Dark.xaml	Consistent additions for RepeatButton/ToggleButton but removal for Expander controls.
ToggleButton.xaml, RepeatButton.xaml, Expander.xaml	Standalone style files add the property for ToggleButton/RepeatButton; Expander style removals noted.

Comments suppressed due to low confidence (1)

src/Microsoft.DotNet.Wpf/src/Themes/PresentationFramework.Fluent/Styles/Expander.xaml:337

• This change removes the RecognizesAccessKey attribute from the Expander style, which is unexpected given the PR description. Please update the Expander style to include RecognizesAccessKey="True".

<ContentPresenter x:Name="ContentPresenter"

[Copilot]

The RecognizesAccessKey attribute is removed from the Expander ContentPresenter here, which conflicts with the PR description stating it should be added. Consider re-adding RecognizesAccessKey="True" for consistency across controls.

Suggested change

	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" />
	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" RecognizesAccessKey="True" />

[Copilot]

The RecognizesAccessKey attribute has been removed from the Expander ContentPresenter, which appears inconsistent with the intended update. Please confirm if the property should be added instead.

Suggested change

	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" />
	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" RecognizesAccessKey="True" />

[Copilot]

Similar to the other themes, the RecognizesAccessKey property is removed from the Expander template. Re-add RecognizesAccessKey="True" to match the PR requirements.

Suggested change

	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" />
	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" RecognizesAccessKey="True" />

[Copilot]

The removal of RecognizesAccessKey in the Expander ContentPresenter here deviates from the PR’s goal; consider adding it back for consistency.

Suggested change

	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" />
	<ContentPresenter x:Name="ContentPresenter" Margin="{TemplateBinding Padding}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}" Content="{TemplateBinding Content}" RecognizesAccessKey="True" />

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 2.98754%. Comparing base (b4d57bf) to head (0c4dacd).

Additional details and impacted files

@@             Coverage Diff             @@
##               main     #10932   +/-   ##
===========================================
  Coverage   2.98754%   2.98754%           
===========================================
  Files          3319       3319           
  Lines        664894     664894           
  Branches      74674      74674           
===========================================
  Hits          19864      19864           
  Misses       644849     644849           
  Partials        181        181           

Flag	Coverage Δ
Debug	2.98754% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.