Windows: Ensure layouts without background participate in hit testing

[jpd21122012]

On Windows, panels with a null Background do not participate in hit testing.
This causes TapGestureRecognizer to not fire when layouts such as Grid, ContentView, or other panels do not explicitly define a background.

As a result, tapping on elements without a background does not trigger gesture recognizers, even though the same scenario works correctly on other platforms.

This change ensures that when a layout's background is null, a transparent background is applied internally so the element participates in hit testing. This allows gesture recognizers such as TapGestureRecognizer to function correctly without requiring developers to explicitly set a background.

The behavior now aligns with other MAUI platforms where layouts without backgrounds can still receive gestures.

Changes

Ensures Panel elements on Windows receive a transparent background when view.Background is null.

This allows layouts without explicit backgrounds to participate in hit testing and receive gesture events.

Tested scenarios

Verified using a simple repro:

Grid
└ ContentView
└ TapGestureRecognizer
Case A

Grid with background → Tap works.

Case B

ContentView with background → Tap works.

Case C

No background defined → Tap now works correctly.

Issue

Fixes #32279

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34364

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34364"

[jpd21122012]

Hi, just checking if this PR could be reviewed for the upcoming 10.6 servicing release.

This change ensures that layouts without a background still participate in hit testing on Windows, which aligns with expected interaction behavior.

The fix is minimal and scoped to input handling, without affecting public APIs, so it should be safe for servicing.

Let me know if any adjustments or additional validation are needed 👍

[kubaflo]

Could you please review the AI's summary?

[jpd21122012]

Could you please review the AI's summary?

Thanks for taking a look!

I reviewed the AI summary and here’s my understanding:

• The core issue is that, on Windows, layouts without a background do not participate in hit testing, which prevents gesture recognizers from working as expected.
• The current fix ensures a transparent background is applied when the MAUI background is null, allowing the layout to participate in hit testing consistently.

Regarding the points raised:

• Test coverage: I agree that adding a regression test would be valuable, and I can work on adding one for this scenario.
• Scope of the fix: The current approach applies a general solution to ensure consistent behavior across layouts. I chose this to keep the fix simple and reliable, without introducing gesture-specific conditions that could add complexity or edge cases.
• The alternative (gesture-scoped fallback) could be explored, but it would require more targeted logic and potentially more maintenance overhead.

Let me know if you’d prefer that I:

1. Add test coverage only, or
2. Also refine the fix to be more narrowly scoped

[kubaflo]

If you could add a test that would be awesome

[jpd21122012]

If you could add a test that would be awesome

Thanks! I’ve added a UITest to cover this scenario.

The test verifies that layouts without a background still receive tap input by attaching a TapGestureRecognizer and asserting the result through a label update. I also included a control case with an explicit background to ensure existing behavior remains unchanged

[Copilot]

Pull request overview

This PR addresses a Windows-specific hit-testing behavior where XAML Panel elements with a null background don’t participate in hit testing, preventing gesture recognizers (e.g., TapGestureRecognizer) from firing when layouts have no explicit background. The change applies a transparent background internally to ensure the platform view participates in hit testing, aligning Windows behavior with other MAUI platforms.

Changes:

• Update Windows ViewExtensions.UpdatePlatformViewBackground to force a transparent Panel.Background when view.Background is null.
• Add a new HostApp issue page (Issue32279) demonstrating tap behavior with/without explicit background.
• Add an Appium UI test (Issue32279) validating tap behavior in both scenarios.

Reviewed changes

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

File	Description
src/Core/src/Platform/Windows/ViewExtensions.cs	Forces Panel to have a transparent background when MAUI background is null to enable hit testing for gestures.
src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs	Adds a repro page for tap gestures with/without background.
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs	Adds Appium tests to validate tap gestures in both cases.

[jpd21122012]

🤖 AI Summary

📊 Expand Full Review — bc6627c · Remove tap target explanatory comments from labels

Thanks for the feedback!

I’ve updated the test to use ContentView so it now exercises the ContentPanel code path, which matches the original issue scenario.

I also scoped the fix specifically to ContentPanel and added a guard to avoid overriding existing platform backgrounds.

Both tests now fail without the fix and pass with it locally

[kubaflo]

/review -b feature/refactor-copilot-yml

[kubaflo]

/review -b feature/refactor-copilot-yml

[MauiBot]

🤖 Automated review — alternative fix proposed

The expert-reviewer evaluation compared the PR fix against #1 automatically generated candidates and selected try-fix-1 as the strongest fix.

Why: try-fix-1 preserves the existing Panel.Background rendering path while adding a transparent fallback for ContentPanel hit testing. The raw PR failed the supplied gate and carries a non-null background regression risk, while try-fix-1 has the safest recorded implementation and a passing Windows targeted test result.

Please consider applying the candidate diff below (or use it as guidance). Once you push an update, this workflow will re-trigger and re-evaluate.

Candidate diff (`try-fix-1`)

diff --git a/src/Core/src/Platform/Windows/ViewExtensions.cs b/src/Core/src/Platform/Windows/ViewExtensions.cs
index 18fea5a6b1..1e4ce0e7ec 100644
--- a/src/Core/src/Platform/Windows/ViewExtensions.cs
+++ b/src/Core/src/Platform/Windows/ViewExtensions.cs
@@ -256,7 +256,13 @@ namespace Microsoft.Maui.Platform
 			else if (platformView is Border border)
 				border.UpdateBackground(view.Background);
 			else if (platformView is Panel panel)
-				panel.UpdateBackground(view.Background);
+			{
+				// ContentPanel (used by ContentView) needs a transparent fallback background
+				// so that hit testing works even when no explicit Background is set.
+				// A null WinUI Background causes the panel to be invisible to pointer input.
+				var defaultBrush = panel is ContentPanel ? new SolidColorBrush(UI.Colors.Transparent) : null;
+				panel.UpdateBackground(view.Background, defaultBrush);
+			}
 		}
 
 		internal static void UpdatePlatformViewBackground(this FrameworkElement platformView, IView view, Brush? defaultBrush = null)
@@ -268,7 +274,10 @@ namespace Microsoft.Maui.Platform
 			else if (platformView is Border border)
 				border.UpdateBackground(view.Background, defaultBrush);
 			else if (platformView is Panel panel)
-				panel.UpdateBackground(view.Background, defaultBrush);
+			{
+				var effectiveBrush = defaultBrush ?? (panel is ContentPanel ? new SolidColorBrush(UI.Colors.Transparent) : null);
+				panel.UpdateBackground(view.Background, effectiveBrush);
+			}
 		}

[MauiBot]

🤖 Automated review — alternative fix proposed

The expert-reviewer evaluation compared the PR fix against #3 automatically generated candidates and selected try-fix-3 as the strongest fix.

Why: try-fix-3 won because it is the only candidate with passing targeted Windows regression validation and it fixes the ContentPanel hit-test invariant at the receiver, surviving paths that clear Background back to null. Failed candidates are ranked lower per the regression-test rule.

Please consider applying the candidate diff below (or use it as guidance). Once you push an update, this workflow will re-trigger and re-evaluate.

Candidate diff (`try-fix-3`)

diff --git a/src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs b/src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs
index 538e5b0258..ba530d92fe 100644
--- a/src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs
+++ b/src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs
@@ -3,8 +3,8 @@ namespace Maui.Controls.Sample.Issues;
 [Issue(IssueTracker.Github, 32279, "TapGestureRecognizer does not work on layouts without a Background on Windows", PlatformAffected.UWP)]
 public class Issue32279 : TestContentPage
 {
-	const string TapTargetNoBackground = "TapTargetNoBackground";
-	const string TapTargetWithBackground = "TapTargetWithBackground";
+	const string TapAnchorNoBackground = "TapAnchorNoBackground";
+	const string TapAnchorWithBackground = "TapAnchorWithBackground";
 	const string ResultLabelNoBackground = "ResultLabelNoBackground";
 	const string ResultLabelWithBackground = "ResultLabelWithBackground";
 
@@ -22,16 +22,15 @@ public class Issue32279 : TestContentPage
 
 		var contentViewNoBackground = new ContentView
 		{
-			HeightRequest = 100,
+			HeightRequest = 200,
 			WidthRequest = 300,
 			Content = new Label
 			{
-				Text = "Tap me (no background)",
-				AutomationId = TapTargetNoBackground,
-				VerticalOptions = LayoutOptions.Fill,
+				Text = "Tap below me (no background)",
+				AutomationId = TapAnchorNoBackground,
+				VerticalOptions = LayoutOptions.Start,
 				HorizontalOptions = LayoutOptions.Fill,
 				HorizontalTextAlignment = TextAlignment.Center,
-				VerticalTextAlignment = TextAlignment.Center,
 			}
 		};
 
@@ -50,17 +49,16 @@ public class Issue32279 : TestContentPage
 
 		var contentViewWithBackground = new ContentView
 		{
-			HeightRequest = 100,
+			HeightRequest = 200,
 			WidthRequest = 300,
 			BackgroundColor = Colors.LightGray,
 			Content = new Label
 			{
-				Text = "Tap me (with background)",
-				AutomationId = TapTargetWithBackground,
-				VerticalOptions = LayoutOptions.Fill,
+				Text = "Tap below me (with background)",
+				AutomationId = TapAnchorWithBackground,
+				VerticalOptions = LayoutOptions.Start,
 				HorizontalOptions = LayoutOptions.Fill,
 				HorizontalTextAlignment = TextAlignment.Center,
-				VerticalTextAlignment = TextAlignment.Center,
 			}
 		};
 
diff --git a/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs b/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs
index ca235e23ef..17535b2f57 100644
--- a/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs
+++ b/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs
@@ -6,6 +6,11 @@ namespace Microsoft.Maui.TestCases.Tests.Issues;
 
 public class Issue32279 : _IssuesUITest
 {
+	const string TapAnchorNoBackground = "TapAnchorNoBackground";
+	const string TapAnchorWithBackground = "TapAnchorWithBackground";
+	const string ResultLabelNoBackground = "ResultLabelNoBackground";
+	const string ResultLabelWithBackground = "ResultLabelWithBackground";
+
 	public Issue32279(TestDevice device) : base(device) { }
 
 	public override string Issue => "TapGestureRecognizer does not work on layouts without a Background on Windows";
@@ -14,9 +19,9 @@ public class Issue32279 : _IssuesUITest
 	[Category(UITestCategories.Gestures)]
 	public void TapOnLayoutWithNoBackgroundShouldWork()
 	{
-		App.WaitForElement("TapTargetNoBackground");
-		App.Tap("TapTargetNoBackground");
-		var result = App.FindElement("ResultLabelNoBackground").GetText();
+		var anchor = App.WaitForElement(TapAnchorNoBackground).GetRect();
+		App.TapCoordinates(anchor.CenterX(), anchor.Y + anchor.Height + 50);
+		var result = App.FindElement(ResultLabelNoBackground).GetText();
 		Assert.That(result, Is.EqualTo("Tapped"));
 	}
 
@@ -24,9 +29,9 @@ public class Issue32279 : _IssuesUITest
 	[Category(UITestCategories.Gestures)]
 	public void TapOnLayoutWithBackgroundShouldWork()
 	{
-		App.WaitForElement("TapTargetWithBackground");
-		App.Tap("TapTargetWithBackground");
-		var result = App.FindElement("ResultLabelWithBackground").GetText();
+		var anchor = App.WaitForElement(TapAnchorWithBackground).GetRect();
+		App.TapCoordinates(anchor.CenterX(), anchor.Y + anchor.Height + 50);
+		var result = App.FindElement(ResultLabelWithBackground).GetText();
 		Assert.That(result, Is.EqualTo("Tapped"));
 	}
 }
\ No newline at end of file
diff --git a/src/Core/src/Platform/Windows/ContentPanel.cs b/src/Core/src/Platform/Windows/ContentPanel.cs
index 61c4e6677e..8cc677583b 100644
--- a/src/Core/src/Platform/Windows/ContentPanel.cs
+++ b/src/Core/src/Platform/Windows/ContentPanel.cs
@@ -10,6 +10,7 @@ using Microsoft.Maui.Graphics.Platform;
 using Microsoft.UI.Composition;
 using Microsoft.UI.Xaml;
 using Microsoft.UI.Xaml.Hosting;
+using Microsoft.UI.Xaml.Media;
 using Microsoft.UI.Xaml.Shapes;
 
 namespace Microsoft.Maui.Platform
@@ -71,6 +72,24 @@ namespace Microsoft.Maui.Platform
 			EnsureBorderPath(containsCheck: false);
 
 			SizeChanged += ContentPanelSizeChanged;
+			RegisterPropertyChangedCallback(BackgroundProperty, OnBackgroundPropertyChanged);
+			EnsureHitTestBackground();
+		}
+
+		static void OnBackgroundPropertyChanged(DependencyObject dependencyObject, DependencyProperty dependencyProperty)
+		{
+			if (dependencyObject is ContentPanel contentPanel)
+			{
+				contentPanel.EnsureHitTestBackground();
+			}
+		}
+
+		void EnsureHitTestBackground()
+		{
+			if (Background == null)
+			{
+				Background = new SolidColorBrush(UI.Colors.Transparent);
+			}
 		}
 
 		void ContentPanelSizeChanged(object sender, SizeChangedEventArgs e)
diff --git a/src/Core/src/Platform/Windows/ViewExtensions.cs b/src/Core/src/Platform/Windows/ViewExtensions.cs
index 439dca88ba..18fea5a6b1 100644
--- a/src/Core/src/Platform/Windows/ViewExtensions.cs
+++ b/src/Core/src/Platform/Windows/ViewExtensions.cs
@@ -255,19 +255,8 @@ namespace Microsoft.Maui.Platform
 				control.UpdateBackground(view.Background);
 			else if (platformView is Border border)
 				border.UpdateBackground(view.Background);
-			else if (platformView is ContentPanel contentPanel)
-			{
-				contentPanel.UpdateBackground(view.Background);
-
-				if (view.Background == null && contentPanel.Background == null)
-				{
-					contentPanel.Background = new SolidColorBrush(UI.Colors.Transparent);
-				}
-			}
 			else if (platformView is Panel panel)
-			{
 				panel.UpdateBackground(view.Background);
-			}
 		}
 
 		internal static void UpdatePlatformViewBackground(this FrameworkElement platformView, IView view, Brush? defaultBrush = null)

[kubaflo]

Could you please check the ai's suggestions?

[jpd21122012]

Could you please check the ai's suggestions?

Yes — I reviewed the AI suggestions and applied the recommended changes.

The implementation was updated to move the transparent hit-test fallback behavior into ContentPanel itself instead of handling it in ViewExtensions, which keeps the hit-testing invariant preserved even if the background is later reset to null.

I also updated the regression tests to validate taps against the actual ContentView surface rather than the child label, matching the real issue scenario more accurately.

Additionally, I validated the updated Issue32279 tests locally on Windows and both are now passing successfully.

[kubaflo]

/review -b feature/refactor-copilot-yml -p windows

[MauiBot]

🤖 AI Summary

👋 @jpd21122012 — new AI review results are available. Please review the latest session below.

📊 Review Session — be6295c · Move hit test fallback behavior into ContentPanel · 2026-05-26 23:27 UTC

🚦 Gate — Test Before & After Fix

Gate Result: ✅ PASSED

Platform: WINDOWS · Base: main · Merge base: b0ea772f

Test	Without Fix (expect FAIL)	With Fix (expect PASS)
🖥️ Issue32279 Issue32279	✅ FAIL — 453s	✅ PASS — 433s

🔴 Without fix — 🖥️ Issue32279: FAIL ✅ · 453s

  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics.Win2D -> D:\a\1\s\artifacts\bin\Graphics.Win2D\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> D:\a\1\s\artifacts\bin\Microsoft.AspNetCore.Components.WebView.Maui\Debug\net10.0-windows10.0.19041.0\Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Foldable -> D:\a\1\s\artifacts\bin\Controls.Foldable\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Foldable.dll
  Controls.TestCases.HostApp -> D:\a\1\s\artifacts\bin\Controls.TestCases.HostApp\Debug\net10.0-windows10.0.19041.0\win-x64\Controls.TestCases.HostApp.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:05:32.26
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  Controls.CustomAttributes -> D:\a\1\s\artifacts\bin\Controls.CustomAttributes\Debug\net10.0\Controls.CustomAttributes.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0\Microsoft.Maui.dll
  Controls.Core.Design -> D:\a\1\s\artifacts\bin\Controls.Core.Design\Debug\net472\Microsoft.Maui.Controls.DesignTools.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0\Microsoft.Maui.Controls.dll
  UITest.Core -> D:\a\1\s\artifacts\bin\UITest.Core\Debug\net10.0\UITest.Core.dll
  UITest.Appium -> D:\a\1\s\artifacts\bin\UITest.Appium\Debug\net10.0\UITest.Appium.dll
  VisualTestUtils -> D:\a\1\s\artifacts\bin\VisualTestUtils\Debug\netstandard2.0\VisualTestUtils.dll
  UITest.NUnit -> D:\a\1\s\artifacts\bin\UITest.NUnit\Debug\net10.0\UITest.NUnit.dll
  VisualTestUtils.MagickNet -> D:\a\1\s\artifacts\bin\VisualTestUtils.MagickNet\Debug\netstandard2.0\VisualTestUtils.MagickNet.dll
  UITest.Analyzers -> D:\a\1\s\artifacts\bin\UITest.Analyzers\Debug\netstandard2.0\UITest.Analyzers.dll
  Controls.TestCases.WinUI.Tests -> D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
Test run for D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll (.NETCoreApp,Version=v10.0)
VSTest version 18.0.1 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
   NUnit3TestExecutor discovered 2 of 2 NUnit test cases using Current Discovery mode, Non-Explicit run
>>>>> 5/26/2026 9:31:51 PM FixtureSetup for Issue32279(Windows)
>>>>> 5/26/2026 9:32:00 PM TapOnLayoutWithBackgroundShouldWork Start
>>>>> 5/26/2026 9:32:02 PM TapOnLayoutWithBackgroundShouldWork Stop
>>>>> 5/26/2026 9:32:02 PM TapOnLayoutWithNoBackgroundShouldWork Start
  Passed TapOnLayoutWithBackgroundShouldWork [1 s]
>>>>> 5/26/2026 9:32:03 PM TapOnLayoutWithNoBackgroundShouldWork Stop
>>>>> 5/26/2026 9:32:03 PM Log types: 
  Failed TapOnLayoutWithNoBackgroundShouldWork [1 s]
  Error Message:
     Assert.That(result, Is.EqualTo("Tapped"))
  Expected string length 6 but was 7. Strings differ at index 0.
  Expected: "Tapped"
  But was:  "Waiting"
  -----------^

  Stack Trace:
     at Microsoft.Maui.TestCases.Tests.Issues.Issue32279.TapOnLayoutWithNoBackgroundShouldWork() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs:line 29

1)    at Microsoft.Maui.TestCases.Tests.Issues.Issue32279.TapOnLayoutWithNoBackgroundShouldWork() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs:line 29


NUnit Adapter 4.5.0.0: Test execution complete
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.8.2+699d445a1a (64-bit .NET 10.0.0)
[xUnit.net 00:00:00.11]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.30]   Discovered:  Controls.TestCases.WinUI.Tests
Results File: D:\a\1\s\CustomAgentLogsTmp\UITests\TestResults\Issue32279.trx

Total tests: 2
     Passed: 1
     Failed: 1
Test Run Failed.
 Total time: 24.5194 Seconds
>>> TRX_RESULT_FILE: D:\a\1\s\CustomAgentLogsTmp\UITests\TestResults\Issue32279.trx

🟢 With fix — 🖥️ Issue32279: PASS ✅ · 433s

  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics.Win2D -> D:\a\1\s\artifacts\bin\Graphics.Win2D\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Foldable -> D:\a\1\s\artifacts\bin\Controls.Foldable\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Foldable.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> D:\a\1\s\artifacts\bin\Microsoft.AspNetCore.Components.WebView.Maui\Debug\net10.0-windows10.0.19041.0\Microsoft.AspNetCore.Components.WebView.Maui.dll
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  Controls.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.dll
  Controls.TestCases.HostApp -> D:\a\1\s\artifacts\bin\Controls.TestCases.HostApp\Debug\net10.0-windows10.0.19041.0\win-x64\Controls.TestCases.HostApp.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:05:24.97
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0\Microsoft.Maui.dll
  Controls.CustomAttributes -> D:\a\1\s\artifacts\bin\Controls.CustomAttributes\Debug\net10.0\Controls.CustomAttributes.dll
  Controls.Core.Design -> D:\a\1\s\artifacts\bin\Controls.Core.Design\Debug\net472\Microsoft.Maui.Controls.DesignTools.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.80-ci+azdo.14198557
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0\Microsoft.Maui.Controls.dll
  UITest.Core -> D:\a\1\s\artifacts\bin\UITest.Core\Debug\net10.0\UITest.Core.dll
  UITest.Appium -> D:\a\1\s\artifacts\bin\UITest.Appium\Debug\net10.0\UITest.Appium.dll
  UITest.NUnit -> D:\a\1\s\artifacts\bin\UITest.NUnit\Debug\net10.0\UITest.NUnit.dll
  VisualTestUtils -> D:\a\1\s\artifacts\bin\VisualTestUtils\Debug\netstandard2.0\VisualTestUtils.dll
  VisualTestUtils.MagickNet -> D:\a\1\s\artifacts\bin\VisualTestUtils.MagickNet\Debug\netstandard2.0\VisualTestUtils.MagickNet.dll
  UITest.Analyzers -> D:\a\1\s\artifacts\bin\UITest.Analyzers\Debug\netstandard2.0\UITest.Analyzers.dll
  Controls.TestCases.WinUI.Tests -> D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
Test run for D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll (.NETCoreApp,Version=v10.0)
VSTest version 18.0.1 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
   NUnit3TestExecutor discovered 2 of 2 NUnit test cases using Current Discovery mode, Non-Explicit run
>>>>> 5/26/2026 9:39:04 PM FixtureSetup for Issue32279(Windows)
>>>>> 5/26/2026 9:39:15 PM TapOnLayoutWithBackgroundShouldWork Start
>>>>> 5/26/2026 9:39:16 PM TapOnLayoutWithBackgroundShouldWork Stop
>>>>> 5/26/2026 9:39:16 PM TapOnLayoutWithNoBackgroundShouldWork Start
  Passed TapOnLayoutWithBackgroundShouldWork [965 ms]
>>>>> 5/26/2026 9:39:16 PM TapOnLayoutWithNoBackgroundShouldWork Stop
  Passed TapOnLayoutWithNoBackgroundShouldWork [664 ms]
NUnit Adapter 4.5.0.0: Test execution complete
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.8.2+699d445a1a (64-bit .NET 10.0.0)
[xUnit.net 00:00:00.16]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.36]   Discovered:  Controls.TestCases.WinUI.Tests
Results File: D:\a\1\s\CustomAgentLogsTmp\UITests\TestResults\Issue32279.trx

Test Run Successful.
Total tests: 2
     Passed: 2
 Total time: 25.7725 Seconds
>>> TRX_RESULT_FILE: D:\a\1\s\CustomAgentLogsTmp\UITests\TestResults\Issue32279.trx

📁 Fix files reverted (2 files)

• eng/pipelines/ci-copilot.yml
• src/Core/src/Platform/Windows/ContentPanel.cs

---

🧪 UI Tests — Gestures,ViewBaseTests

Detected UI test categories: Gestures,ViewBaseTests

✅ Deep UI tests — 164 passed, 0 failed across 2 categories on platform-pool agent (replaces in-process counts above).

🧪 UI Test Execution Results (deep, platform pool)

Category	Tests	Snapshot diffs
Gestures	49/49 ✓	—
ViewBaseTests	115/115 ✓	—
📎 Download drop-deep-uitests artifact (TRX + snapshot diffs)

---

🔍 Regression Cross-Reference

🔍 Regression Cross-Reference

🟢 No regression risks detected. No labeled bug-fix PRs in the last 6 months touched the modified files.

---

🔍 Pre-Flight — Context & Validation

Issue: #32279 - [Windows] TapGestureRecognizer does NOT work on a ContentView without Background
PR: #34364 - Windows: Ensure layouts without background participate in hit testing
Platforms Affected: Windows
Files Changed: 1 implementation, 2 test

Key Findings

• WinUI panels with Background == null do not receive hit testing on empty surface area; the repro ContentView tap leaves the result label at Waiting without a fix.
• The PR changes src/Core/src/Platform/Windows/ContentPanel.cs so ContentPanel.Background is forced to a transparent brush whenever it becomes null.
• Regression coverage adds a HostApp issue page and Windows Appium tests for ContentView with no background and with an explicit background.
• Prior issue discussion noted the same transparent-background workaround already used by LayoutPanel, while cautioning against unnecessary extra layers.
• Gate result supplied by the caller: tests fail without fix and pass with fix; gate artifacts were preserved and not regenerated.

Code Review Summary

Verdict: LGTM
Confidence: high
Errors: 0 | Warnings: 0 | Suggestions: 0

Key code review findings:

• No actionable findings. The risk of broadly changing ContentPanel hit testing is intentional, visually neutral, and consistent with existing Windows LayoutPanel behavior.

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #34364	Enforce a transparent native ContentPanel.Background whenever it is null, using a property-changed callback so later clears are repaired.	PASSED (Gate)	src/Core/src/Platform/Windows/ContentPanel.cs; src/Controls/tests/TestCases.HostApp/Issues/Issue32279.cs; src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue32279.cs	Original PR; gate passed on Windows and targeted UI regression passed.

---

🔬 Code Review — Deep Analysis

Code Review PR #34364

Independent Assessment

What this changes: Windows ContentPanel now substitutes a transparent WinUI background whenever its native Background is null, making empty ContentView/ContentPanel surface areas hit-testable. Adds UI regression tests for tapping ContentView with and without explicit background.
Inferred motivation: WinUI panels with Background == null do not receive hit tests in empty space, so gestures miss unless tapping child content.

Reconciliation with PR Narrative

Author claims: Fixes Windows tap gestures for layouts without backgrounds by applying transparent background internally.
Agreement/disagreement: Matches for ContentPanel/ContentView. Broader "Grid/layout" wording is acceptable because LayoutPanel already has an equivalent transparent-background hit-test pattern.

Findings

No actionable findings.

Devil's Advocate

The main risk is changing all ContentPanel instances from null to transparent background, affecting hit-testing broadly. That appears intentional, visually neutral, and consistent with existing LayoutPanel behavior. The callback self-mutates Background, but converges immediately once non-null.

Verdict: LGTM

Confidence: high
Summary: The fix is scoped, consistent with existing Windows MAUI patterns, and covered by a regression UI test. Latest check runs are successful. Wrote CustomAgentLogsTmp\PRState\34364\PRAgent\inline-findings.json as []; no GitHub comments posted.

---

🔧 Fix — Analysis & Comparison

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
1	try-fix-1	Add a ContentPanel-specific branch in ViewExtensions.UpdatePlatformViewBackground that supplies a transparent default brush through the existing Windows background update pipeline.	PASSED	1 file	Works and follows the defaultBrush pipeline, but only protects mapper/update calls; direct native Background = null can bypass it.
2	try-fix-2	Add a Windows-only ContentViewHandler.MapBackground mapper that passes a transparent default brush to UpdatePlatformViewBackground.	PASSED	3 files	Narrowest functional scope, but introduces a public static mapper method requiring PublicAPI.Unshipped.txt; less defensive than the PR.
3	try-fix-3	Change ControlExtensions.UpdateBackground(this Panel, ...) so ContentPanel uses a cached transparent fallback when paint/defaultBrush are null.	PASSED	2 files	Centralizes the fallback at the Panel background helper and avoids public API changes, but still relies on setting Panel.Background.
4	try-fix-4	Use ContentPanel's existing _borderPath child as a transparent rectangular hit-test surface without setting Panel.Background.	FAILED	1 file	Build succeeded, but TapOnLayoutWithNoBackgroundShouldWork failed; result stayed Waiting, disproving the child-path strategy.
PR	PR #34364	Self-heal ContentPanel.Background in the constructor via BackgroundProperty callback, replacing null native background with transparent.	PASSED (Gate)	3 files	Most defensive passing solution; survives later paths that clear native Background back to null.

Cross-Pollination

Model	Round	New Ideas?	Details
claude-opus-4.6	2	No	NO NEW IDEAS
claude-opus-4.7	2	No	NO NEW IDEAS
gpt-5.3-codex	2	No	NO NEW IDEAS
gpt-5.5	2	No	NO NEW IDEAS all passing candidates require a non-null ContentPanel.Background; the only tested non-background strategy failed.

Exhausted: Yes
Selected Fix: PR #34364 The PR's ContentPanel self-healing callback is the most robust passing fix. Attempts 1-3 also pass, but they depend on specific MAUI update/mapper paths and do not protect against later native Background clears. Attempt 4 demonstrated that avoiding Panel.Background by using the child path does not satisfy the regression test.

Candidate Details

try-fix-1

Artifacts: CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix-1/content.md and CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix/attempt-1/.

try-fix-2

Artifacts: CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix-2/content.md and CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix/attempt-2/.

try-fix-3

Artifacts: CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix-3/content.md and CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix/attempt-3/.

try-fix-4

Artifacts: CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix-4/content.md and CustomAgentLogsTmp/PRState/34364/PRAgent/try-fix/attempt-4/.

---

📋 Report — Final Recommendation

Comparative Report: PR #34364

Candidates Compared

Rank	Candidate	Test Result	Assessment
1	pr	PASSED	Most defensive passing solution. It self-heals ContentPanel.Background whenever it becomes null, covering construction, mapper updates, and any later code path that clears the native background.
1	pr-plus-reviewer	PASSED	Expert reviewer found no actionable issues, so this is identical to pr. It is tied with the raw PR fix and does not introduce additional changes.
3	try-fix-3	PASSED	Centralizes the transparent fallback in ControlExtensions.UpdateBackground(this Panel, ...) for ContentPanel. This is clean and avoids public API changes, but it only applies when the MAUI panel-background helper is used.
4	try-fix-1	PASSED	Adds a ContentPanel branch to the Windows ViewExtensions.UpdatePlatformViewBackground pipeline. It works for mapper/update calls, but is less defensive than the PR because direct native Background = null paths bypass it.
5	try-fix-2	PASSED	Narrowly scopes the fallback to Windows ContentViewHandler.MapBackground, but requires a public mapper API entry and is the least defensive passing candidate because it only protects ContentView background mapping.
6	try-fix-4	FAILED	Uses the existing _borderPath child as a transparent hit-test surface, but regression testing failed: TapOnLayoutWithNoBackgroundShouldWork left the result at Waiting. Per the ranking rule, this failed candidate ranks below all passing candidates.

Analysis

All passing candidates make WinUI see a non-null background for the relevant surface. The important distinction is where that guarantee is enforced.

The PR fix enforces the guarantee at the ContentPanel itself. That is the most robust location because it is independent of which mapper, helper, or update pipeline attempts to clear or omit the native background. The property-changed callback is also narrowly scoped: it only acts when Background is null, and it leaves explicit backgrounds untouched.

try-fix-1, try-fix-2, and try-fix-3 all passed the targeted regression tests, but each depends on a specific MAUI update path. They are valid alternatives if minimizing ContentPanel behavior changes were the only priority, but they do not protect as well against future or external code paths that set the native Background back to null. try-fix-2 also adds public API surface for a mapper override, making it less attractive for a bug fix.

try-fix-4 is not viable because it failed the regression test. Even though it avoided changing Panel.Background, the transparent child path did not cause the ContentPanel gesture recognizer to receive taps over the empty area.

Winning Candidate

Winner: pr

The raw PR fix wins because it is the most defensive passing candidate and the expert reviewer found no actionable changes to apply. pr-plus-reviewer is equivalent after review, but the canonical submitted PR fix should be selected because no reviewer-applied delta exists.

---