[Windows] Fix CarouselView EmptyView display when filtering to zero items

[Shalini-Ashokan]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Issue Details

On Windows platforms, both the empty view and a carousel item are displayed simultaneously when a search returns no results.

Root Cause

When filtering results to zero items in CarouselView on Windows, the handler correctly sets the EmptyView to visible but does not fully reset the current item state. As a result, both the empty view and the last carousel item remain visible.

Description of Change

Set the ItemTemplate as null and disables looping to ensure the UI is properly cleared when displaying the empty view.

Validated the behavior in the following platforms

• Android
• Windows
• iOS
• Mac

Issues Fixed

Fixes #7150

Output ScreenShot

Before	After
BeforeFix-7150.mp4	AfterFix-7150.mp4

[dotnet-policy-service]

Hey there @@Shalini-Ashokan! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

There are some CarouselView failing tests on Windows:

Could you review if are related with the changes. Looks like some tests are crashing the App.

For example, VerifyCarouselViewItemsRenderAfterBinding
The app was expected to be running still, investigate as possible crash

Could you review if are related with the changes?

[Shalini-Ashokan]

There are some CarouselView failing tests on Windows: Could you review if are related with the changes. Looks like some tests are crashing the App.

For example, VerifyCarouselViewItemsRenderAfterBinding The app was expected to be running still, investigate as possible crash

Could you review if are related with the changes?

@jsuarezruiz, Yes, the test failures are related to my changes. I have updated the logic specifically for the looping scenario to resolve the failures.

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

@Shalini-Ashokan Could you rebase and fix the conflict?

[Shalini-Ashokan]

@Shalini-Ashokan Could you rebase and fix the conflict?

@jsuarezruiz, I have rebased the branch and resolved the conflicts.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jfversluis]

/rebase

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[MauiBot]

🤖 AI Summary

👋 @Shalini-Ashokan — new AI review results are available. Please review the latest session below.

📊 Review Session — 2ebc190 · Added base snapshot · 2026-05-02 15:53 UTC

---

🚦 Gate — Test Before & After Fix

---

Gate Result: ❌ FAILED

Platform: WINDOWS · Base: main · Merge base: 1463c4c5

🩺 Test filter mismatch — filter Issue7150 matched 0 tests. The test runner produced zero results because no test class or method matched the filter. Common causes: the gate filter was derived from the file name but the actual test class is named differently, or the test was renamed/moved without updating the auto-detection. Verify the test class name matches what the gate is searching for.

Test	Without Fix (expect FAIL)	With Fix (expect PASS)
🖥️ Issue7150 Issue7150	🔍 NO MATCH	🔍 NO MATCH

🔴 Without fix — 🖥️ Issue7150: 🔍 NO MATCH · 541s

  Determining projects to restore...
  Restored D:\a\1\s\src\Controls\src\Core\Controls.Core.csproj (in 48.37 sec).
  Restored D:\a\1\s\src\Controls\Maps\src\Controls.Maps.csproj (in 48.65 sec).
  Restored D:\a\1\s\src\Controls\Foldable\src\Controls.Foldable.csproj (in 431 ms).
  Restored D:\a\1\s\src\Graphics\src\Graphics\Graphics.csproj (in 1.11 sec).
  Restored D:\a\1\s\src\Graphics\src\Graphics.Win2D\Graphics.Win2D.csproj (in 4 ms).
  Restored D:\a\1\s\src\Essentials\src\Essentials.csproj (in 13 ms).
  Restored D:\a\1\s\src\Core\src\Core.csproj (in 911 ms).
  Restored D:\a\1\s\src\Core\maps\src\Maps.csproj (in 21 ms).
  Restored D:\a\1\s\src\BlazorWebView\src\Maui\Microsoft.AspNetCore.Components.WebView.Maui.csproj (in 2.88 sec).
  Restored D:\a\1\s\src\Controls\src\Xaml\Controls.Xaml.csproj (in 19 ms).
  Restored D:\a\1\s\src\Controls\tests\TestCases.HostApp\Controls.TestCases.HostApp.csproj (in 505 ms).
  3 of 14 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  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.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.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.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.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:06:02.34
  Determining projects to restore...
  Restored D:\a\1\s\src\Controls\tests\CustomAttributes\Controls.CustomAttributes.csproj (in 986 ms).
  Restored D:\a\1\s\src\TestUtils\src\VisualTestUtils\VisualTestUtils.csproj (in 3 ms).
  Restored D:\a\1\s\src\TestUtils\src\VisualTestUtils.MagickNet\VisualTestUtils.MagickNet.csproj (in 5.26 sec).
  Restored D:\a\1\s\src\Controls\tests\TestCases.WinUI.Tests\Controls.TestCases.WinUI.Tests.csproj (in 8.02 sec).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Core\UITest.Core.csproj (in 2 ms).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Appium\UITest.Appium.csproj (in 2 ms).
  Restored D:\a\1\s\src\TestUtils\src\UITest.NUnit\UITest.NUnit.csproj (in 2.12 sec).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Analyzers\UITest.Analyzers.csproj (in 4.6 sec).
  7 of 15 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Controls.CustomAttributes -> D:\a\1\s\artifacts\bin\Controls.CustomAttributes\Debug\net10.0\Controls.CustomAttributes.dll
  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.70-ci+azdo.14000271
  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.
D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
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 0 of 0 NUnit test cases using Current Discovery mode, Explicit run
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.08]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.30]   Discovered:  Controls.TestCases.WinUI.Tests
No test matches the given testcase filter `Issue7150` in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll

🟢 With fix — 🖥️ Issue7150: 🔍 NO MATCH · 442s

  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Controls.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.dll
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.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:48.70
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.70-ci+azdo.14000271
  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.70-ci+azdo.14000271
  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.
D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
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 0 of 0 NUnit test cases using Current Discovery mode, Explicit run
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.10]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.33]   Discovered:  Controls.TestCases.WinUI.Tests
No test matches the given testcase filter `Issue7150` in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll

⚠️ Failure Details

• 🔍 Issue7150 without fix: test filter matched 0 tests
  • filter: Issue7150
• 🔍 Issue7150 with fix: test filter matched 0 tests
  • filter: Issue7150

📁 Fix files reverted (3 files)

• eng/pipelines/ci-copilot.yml
• src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs
• src/Controls/src/Core/PublicAPI/net-windows/PublicAPI.Unshipped.txt

---

🧪 UI Tests — Category Detection

---

Detected UI test categories: CarouselView,CollectionView

---

🔍 Pre-Flight — Context & Validation

---

Issue: #7150 - [Windows] [Scenario Day] EmptyView using Template displayed at the same time as the content
PR: #29247 - [Windows] Fix CarouselView EmptyView display when filtering to zero items
Platforms Affected: Windows (primary fix), snapshot tests for Android/iOS/Mac
Files Changed: 2 implementation, 1 test (shared), 1 test (host app), 4 snapshot images

Key Findings

• On Windows with CarouselView.Loop = true, filtering items to zero causes both the EmptyView and the last carousel item to remain visible simultaneously.
• Root cause A: LoopableCollectionView.Count returns FakeCount (655360) when IsLoopingEnabled = true, so the ListViewBase still has items to render even when the actual data is empty. The item renderer displays phantom items via the CarouselItemsViewTemplate.
• Root cause B: The original ComputeVisibleIndexes does args.FirstVisibleItemIndex %= ItemCount without guarding against ItemCount == 0, which causes a DivideByZeroException when all items are filtered out with Loop=true.
• PR fixes both issues: (1) guards ComputeVisibleIndexes with ItemCount > 0, (2) overrides UpdateEmptyViewVisibility to clear ListViewBase.ItemTemplate when the carousel is empty and Loop=true.
• The test (Issue7150.cs) is wrapped in #if TEST_FAILS_ON_WINDOWS — no automated Windows test for a Windows-only fix. The author attributes this to a separate bug ([Testing] Appium test does not perform the tap action with CarouselView. #29245: interaction with elements inside Loop=true CarouselView on Windows).
• Reviewer jsuarezruiz left an unresolved comment: "Because the changes are fixing a bug on Windows, can we have a working test on Windows?" The author says it cannot be done due to [Testing] Appium test does not perform the tap action with CarouselView. #29245. The FilterButton is in a parent Grid row 0 (NOT inside the CarouselView), so the interaction blocker of issue [Testing] Appium test does not perform the tap action with CarouselView. #29245 should not apply.
• Previous CarouselView tests were crashing the app after an earlier version of this fix; the author fixed that by scoping the UpdateEmptyViewVisibility change to loop-only scenarios.
• Gate ❌ FAILED — tests did NOT behave as expected on Windows.

Code Review Summary

Verdict: NEEDS_DISCUSSION
Confidence: medium
Errors: 0 | Warnings: 1 | Suggestions: 2

Key code review findings:

• ⚠️ src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs:86 — UpdateItemTemplate() unconditionally sets ListViewBase.ItemTemplate = CarouselItemsViewTemplate before calling UpdateItemsSource(). When Loop=true and the collection is empty, this creates a brief transient state where the template is non-null until UpdateEmptyViewVisibility() (called from UpdateItemsSource()) sets it back to null. The chain is synchronous so no visible flash occurs, but a guard in UpdateItemTemplate() would make the contract explicit.
• 💡 src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue7150.cs:19 — VerifyScreenshot() lacks retryTimeout; prefer VerifyScreenshot(retryTimeout: TimeSpan.FromSeconds(3)).
• 💡 src/Controls/tests/TestCases.HostApp/Issues/Issue7150.cs:96 — FilterCommand => new Command(FilterItems) allocates a new Command on every binding refresh; should cache as readonly field.
• ⚠️ The Windows test exclusion (#if TEST_FAILS_ON_WINDOWS) is the most significant risk — no automated Windows regression test for a Windows-only fix.

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #29247	Override UpdateEmptyViewVisibility to clear ListViewBase.ItemTemplate when Loop=true + guard ItemCount > 0 in ComputeVisibleIndexes	❌ Gate FAILED	CarouselViewHandler.Windows.cs	Original PR

---

🔬 Code Review — Deep Analysis

---

Code Review — PR #29247

Independent Assessment (code-first, before reading PR narrative)

What this changes:

1. CarouselViewHandler.Windows.cs — adds a > 0 guard in ComputeVisibleIndexes before doing modulo arithmetic on ItemCount, preventing a divide-by-zero when the carousel is empty in loop mode.
2. Overrides UpdateEmptyViewVisibility so that, when Loop=true and CollectionViewSource reports zero items, ListViewBase.ItemTemplate is set to null; it is restored to CarouselItemsViewTemplate when items return. A guard prevents redundant template assignments.
3. Adds a new UI-test host page (Issue7150) with a CarouselView + EmptyView + filter button, and a shared test that screenshots the empty state. The test is excluded on Windows via #if TEST_FAILS_ON_WINDOWS.

Inferred motivation: A Windows-only visual bug where the last carousel item remained visible on screen alongside the EmptyView after items were filtered to zero, because the handler's empty-view path never cleared the WinUI ItemTemplate.

Approach assessment: Sound. On WinUI, a ListView with a non-null ItemTemplate will attempt to render items even when the ICollectionView is empty (especially in carousel/loopable scenarios). Nulling the template is the correct lever. The ItemCount > 0 guard for the modulo is a necessary defensive fix (division-by-zero on empty loop).

---

Reconciliation with PR Narrative

Author claims: Windows CarouselView shows EmptyView and carousel content simultaneously when filtering to zero items. Root cause: handler doesn't reset current-item state when displaying the EmptyView. Fix: set ItemTemplate = null to clear the carousel render surface.

Agreement: Root cause analysis matches the code. Minor wording mismatch — the description says "disables looping" but the fix only nulls the template; _loopableCollectionView.IsLoopingEnabled is never touched.

Existing open thread: @jsuarezruiz raised (unresolved) that the FilterButton is outside the CarouselView so #if TEST_FAILS_ON_WINDOWS shouldn't be needed. The author explains that on Windows, all touch/tap interaction fails when Loop=true due to a separate issue (#29245), making the test unrunnable on Windows regardless of element position. This is the most significant open question on the PR.

---

Findings

⚠️ Warning — UpdateItemTemplate creates a transient empty-state inconsistency

CarouselViewHandler.Windows.cs:86

UpdateItemTemplate unconditionally sets ListViewBase.ItemTemplate = CarouselItemsViewTemplate before chaining into UpdateItemsSource() → UpdateEmptyViewVisibility(). When Loop=true and the collection is empty, the call chain is:

UpdateItemTemplate()
  → ListViewBase.ItemTemplate = CarouselItemsViewTemplate   ← sets it back to non-null
  → UpdateItemsSource()
      → UpdateEmptyViewVisibility()
          → ListViewBase.ItemTemplate = null                ← immediately corrected

Because the whole chain is synchronous, WinUI won't render a frame between the two template assignments, so there is no visible flash. But it violates the contract the new override establishes (template is null when empty in loop mode) for the duration of UpdateItemsSource(). A minimal guard in the override would make it explicit:

protected override void UpdateItemTemplate()
{
    if (Element == null || ListViewBase == null)
        return;

    // Don't restore the carousel template if we're in loop-mode and currently empty;
    // UpdateEmptyViewVisibility (called via UpdateItemsSource below) will set it correctly.
    if (ItemsView?.Loop != true || (CollectionViewSource?.View?.Count ?? 0) > 0)
        ListViewBase.ItemTemplate = CarouselItemsViewTemplate;

    UpdateItemsSource();
}

💡 Suggestion — VerifyScreenshot() lacks retry timeout

[TestCases.Shared.Tests/Tests/Issues/Issue7150.cs:19]

VerifyScreenshot();  // ← no retryTimeout

Per MAUI UI test convention, prefer VerifyScreenshot(retryTimeout: TimeSpan.FromSeconds(3)) to absorb animation-frame timing variance on CI agents.

💡 Suggestion — FilterCommand allocates a new Command on every property access

[TestCases.HostApp/Issues/Issue7150.cs:96]

public ICommand FilterCommand => new Command(FilterItems);

The binding engine reads this getter on each binding refresh, allocating a new Command each time. Prefer a cached backing field:

readonly ICommand _filterCommand;
public ICommand FilterCommand => _filterCommand;

public Issue7150ViewModel()
{
    _filterCommand = new Command(FilterItems);
    // ...
}

---

Devil's Advocate

Challenging the Warning: The UpdateItemTemplate transient issue could only cause a real problem if WinUI's compositor could observe the intermediate state. Since this is all on the UI thread without yielding, it cannot. However, if a future refactor splits the call chain with async/await between ListViewBase.ItemTemplate = … and UpdateItemsSource(), this would become a real bug. The explicit guard is cheap insurance.

Challenging approval: The Windows test exclusion is the genuine risk here. The fix is in CarouselViewHandler.Windows.cs but no test ever runs on Windows for this scenario. If the fix were accidentally reverted, no CI would catch it. The author's argument (blocked by #29245) is fair, but it does mean this PR ships with zero automated Windows regression coverage for its core behavior.

Platform blind spot check: The fix is strictly #Windows. iOS/Android/Mac code paths are untouched. Their snapshot baselines are added, which is correct for the shared test infra.

---

Verdict: NEEDS_DISCUSSION

Confidence: medium

Summary: The fix itself is correct — the ItemTemplate = null approach is the right mechanism for clearing WinUI's carousel render surface in loop-empty state, and the ItemCount > 0 guard closes a latent divide-by-zero. All CI is green. The open question for human judgment is whether to accept the PR without any Windows regression test coverage (blocked by #29245), or require #29245 to be resolved first. The UpdateItemTemplate transient inconsistency is a low-severity cleanup worth addressing before merge, but it does not affect observable behavior.

---

🔧 Fix — Analysis & Comparison

---

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
1	try-fix-1	Fix LoopableCollectionView.Count to report 0 when empty (even with IsLoopingEnabled=true); toggle IsLoopingEnabled + disconnect/reconnect ItemsSource in UpdateEmptyViewVisibility; guard LoopableCollectionView.IndexOf	✅ PASS	CarouselViewHandler.Windows.cs, LoopableCollectionView.cs, Issue7150.cs (test), PublicAPI.Unshipped.txt, Windows snapshot	Root-cause fix at LoopableCollectionView layer; removes #if TEST_FAILS_ON_WINDOWS; known limitation: backward loop scroll starts at index 0 instead of center after empty→non-empty
2	try-fix-2	Dual-layer guard: override UpdateItemTemplate with empty-state guard (code-review suggestion) + override UpdateEmptyViewVisibility to null both ItemTemplate AND ItemsSource	❌ FAIL	CarouselViewHandler.Windows.cs, Issue7150.cs	WinAppDriver UIA hang with 655360 nodes during initial non-empty state (same #29245 root cause); visual fix confirmed via screenshot
3	try-fix-3	Source-update template sync: override UpdateItemsSource/UpdateLoop to sync ItemTemplate with empty state	❌ FAIL	CarouselViewHandler.Windows.cs	Test not found on Windows (test still wrapped in #if TEST_FAILS_ON_WINDOWS which this approach didn't remove)
4	try-fix-4	Comprehensive: ComputeVisibleIndexes guard + UpdateEmptyViewVisibility override (null template + disable IsLoopingEnabled + refresh ItemsSource) + UpdateItemTemplate guard + remove #if TEST_FAILS_ON_WINDOWS	❌ FAIL	CarouselViewHandler.Windows.cs, Issue7150.cs	App unresponsive ~30-40s after filtering to empty when Loop=true; WinAppDriver VerifyScreenshot times out; #29245 confirmed by Loop=true making WinUI app unresponsive
PR	PR #29247	Override UpdateEmptyViewVisibility to set ListViewBase.ItemTemplate=null when Loop=true+empty; restore on non-empty; guard ComputeVisibleIndexes with ItemCount>0	❌ Gate FAILED	CarouselViewHandler.Windows.cs, PublicAPI.Unshipped.txt	Test wrapped in #if TEST_FAILS_ON_WINDOWS; no Windows test for Windows-only fix

Cross-Pollination

Model	Round	New Ideas?	Details
claude-opus-4.6	2	No	Attempt 1 approach is the most complete. LoopableCollectionView.Count truthfulness + ItemsSource disconnect is the right architecture. Backward scroll limitation is an acceptable trade-off. NO NEW IDEAS
claude-sonnet-4.6	2	No	The attempt 2 failure confirmed that nulling ItemTemplate alone (PR approach) cannot prevent WinUI from hanging on 655360 nodes. Attempt 1's LoopableCollectionView change is the correct layer. NO NEW IDEAS
gpt-5.3-codex	2	No	All reasonable architectural alternatives explored. The fundamental issue is LoopableCollectionView.Count = FakeCount when non-empty+Loop=true. NO NEW IDEAS
claude-opus-4.6 (attempt 4)	2	No	Comprehensive fix confirmed visual correctness but app hang is from Loop=true CarouselView itself, not the test approach. NO NEW IDEAS

Exhausted: Yes
Selected Fix: Candidate #1 (try-fix-1) — Only PASS result. Fixes root cause at LoopableCollectionView layer, enables Windows test coverage by removing #if TEST_FAILS_ON_WINDOWS, includes null-safety fix for _vectorChanged?.Invoke.

---

📋 Report — Final Recommendation

---

⚠️ Final Recommendation: REQUEST CHANGES

Phase Status

Phase	Status	Notes
Pre-Flight	✅ COMPLETE	Issue #7150, Windows CarouselView Loop+EmptyView bug
Code Review	NEEDS_DISCUSSION (medium)	0 errors, 1 warning, 2 suggestions
Gate	❌ FAILED	Windows — test excluded via #if TEST_FAILS_ON_WINDOWS
Try-Fix	✅ COMPLETE	4 attempts, 1 passing (try-fix-1)
Report	✅ COMPLETE

Code Review Impact on Try-Fix

The code-review warning about UpdateItemTemplate creating a transient inconsistency was addressed in try-fix-2 (which added the UpdateItemTemplate guard), but try-fix-2 still failed due to WinAppDriver UIA issues. The most impactful insight from code review was the NEEDS_DISCUSSION verdict — specifically that the #if TEST_FAILS_ON_WINDOWS exclusion leaves zero automated Windows regression coverage for a Windows-only fix. Try-fix-1 addressed this directly by fixing the LoopableCollectionView layer and removing the #if guard, enabling a passing Windows test.

Summary

The PR's fix (set ListViewBase.ItemTemplate = null when Loop+empty) is visually correct but gate-fails because the test is excluded on Windows. Try-fix-1 found an alternative that fixes the root cause at the LoopableCollectionView layer, enables a working Windows test, and adds a null-safety fix for _vectorChanged?.Invoke. Try-fix-1 is the winning candidate with its PASS result.

Root Cause

On Windows with CarouselView.Loop=true, LoopableCollectionView.Count returns FakeCount (655360) regardless of actual item count. When items are filtered to zero, the ListViewBase still has 655360 virtual items to render via CarouselItemsViewTemplate, causing the last carousel item to appear alongside the EmptyView. Additionally, ComputeVisibleIndexes performs modulo arithmetic against ItemCount without a zero-guard, causing DivideByZeroException when empty with Loop=true.

Fix Quality

PR's fix: Minimal and targeted — sets ItemTemplate = null when empty+Loop. Prevents ghost rendering without touching LoopableCollectionView. However, the LoopableCollectionView still reports 655360 items (just with no template to render them), which is the root of the WinAppDriver UIA hang described in issue #29245. The PR cannot provide Windows test coverage.

Try-fix-1 (winner): Deeper fix — makes LoopableCollectionView.Count truthful when empty (returns 0 instead of FakeCount), toggles IsLoopingEnabled and disconnects ItemsSource when empty. This is the only approach that produced a PASS result with an enabled Windows test. Known limitation: after empty→non-empty transition, backward loop scroll position starts at index 0 rather than center (~327,680), because UpdateInitialPosition re-centers but the backward direction starts fresh. This is a minor UX degradation for a rare edge case.

---

❌ Deep UI tests — 346 passed, 6 failed across 2 categories on platform-pool agent (replaces in-process counts above).

🧪 UI Test Execution Results (deep, platform pool)

Category	Tests	Snapshot diffs
CarouselView	30/35 (5 ❌)	—
CollectionView	316/328 (1 ❌)	1 diff PNG

❌ CarouselView — 5 failed tests

VerifyCarouselViewWithIsSwipeDisable

OneTimeSetUp: System.TimeoutException : Timed out waiting for Go To Test button to disappear
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2757
   at UITest.Appium.HelperExtensions.WaitForNone(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2793
   at UITest.Appium.HelperExtensions.WaitForNoElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 998
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateTo(IApp app, String text) in /_/src/Controls/tests/TestCases.Shared.Tests/UtilExtensions.cs:line 52
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateToGallery(IApp app, String pag
...

VerifyCarouselViewWithKeepItemInView

OneTimeSetUp: System.TimeoutException : Timed out waiting for Go To Test button to disappear
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2757
   at UITest.Appium.HelperExtensions.WaitForNone(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2793
   at UITest.Appium.HelperExtensions.WaitForNoElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 998
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateTo(IApp app, String text) in /_/src/Controls/tests/TestCases.Shared.Tests/UtilExtensions.cs:line 52
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateToGallery(IApp app, String pag
...

VerifyCarouselViewWithKeepScrollOffset

OneTimeSetUp: System.TimeoutException : Timed out waiting for Go To Test button to disappear
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2757
   at UITest.Appium.HelperExtensions.WaitForNone(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2793
   at UITest.Appium.HelperExtensions.WaitForNoElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 998
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateTo(IApp app, String text) in /_/src/Controls/tests/TestCases.Shared.Tests/UtilExtensions.cs:line 52
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateToGallery(IApp app, String pag
...

VerifyCarouselViewWithRTLFlowDirection

OneTimeSetUp: System.TimeoutException : Timed out waiting for Go To Test button to disappear
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2757
   at UITest.Appium.HelperExtensions.WaitForNone(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2793
   at UITest.Appium.HelperExtensions.WaitForNoElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 998
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateTo(IApp app, String text) in /_/src/Controls/tests/TestCases.Shared.Tests/UtilExtensions.cs:line 52
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateToGallery(IApp app, String pag
...

VerifyCarouselViewWithPeekAreaInsets

OneTimeSetUp: System.TimeoutException : Timed out waiting for Go To Test button to disappear
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2757
   at UITest.Appium.HelperExtensions.WaitForNone(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2793
   at UITest.Appium.HelperExtensions.WaitForNoElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 998
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateTo(IApp app, String text) in /_/src/Controls/tests/TestCases.Shared.Tests/UtilExtensions.cs:line 52
   at Microsoft.Maui.TestCases.Tests.UtilExtensions.NavigateToGallery(IApp app, String pag
...

❌ CollectionView — 1 failed test

VerifyDefaultScrollToRequested

VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: VerifyDefaultScrollToRequested.png (0.52% difference)
If the correct baseline has changed (this isn't a a bug), then update the baseline image.
See test attachment or download the build artifacts to get the new snapshot file.

More info: https://aka.ms/visual-test-workflow
at VisualTestUtils.VisualRegressionTester.Fail(String message) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 162
   at VisualTestUtils.VisualRegressionTester.VerifyMatchesSnapshot(String name, ImageSnapshot actualImage, String environmentName, ITestContext testContext) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 123
   at Microsoft.Maui.TestCases.Tests.UITest.<VerifyScreenshot>g__Verify|13_0(String name, <>c__DisplayClass13_0&) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 477
   at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 ret
...

📎 Download drop-deep-uitests artifact (TRX + snapshot diffs)

[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 is the only candidate that produced a passing test on Windows. It fixes the root cause at the LoopableCollectionView layer by making Count truthful when empty (returns 0 instead of FakeCount=655360), toggles IsLoopingEnabled and disconnects ItemsSource when empty, removes the #if TEST_FAILS_ON_WINDOWS test exclusion, and adds a null-safety fix for _vectorChanged?.Invoke. The PR's approach (ItemTemplate=null only) leaves 655360 phantom nodes in the UIA tree and cannot enable Windows test coverage.

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/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs b/src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs
index 624a1db702..650a339db6 100644
--- a/src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs
+++ b/src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs
@@ -26,6 +26,7 @@ namespace Microsoft.Maui.Controls.Handlers.Items
 WScrollBarVisibility? _verticalScrollBarVisibilityWithoutLoop;
 Size _currentSize;
 bool _isCarouselViewReady;
+bool _updatingEmptyView;
 int _gotoPosition = -1;
 NotifyCollectionChangedEventHandler _collectionChanged;
 readonly WeakNotifyCollectionChangedProxy _proxy = new();
@@ -146,7 +147,7 @@ namespace Microsoft.Maui.Controls.Handlers.Items
 {
 args = base.ComputeVisibleIndexes(args, orientation, advancing);
 
-if (ItemsView.Loop && ItemsView.ItemsSource is not null)
+if (ItemsView.Loop && ItemsView.ItemsSource is not null && ItemCount > 0)
 {
 args.FirstVisibleItemIndex %= ItemCount;
 args.CenterItemIndex %= ItemCount;
@@ -156,6 +157,49 @@ namespace Microsoft.Maui.Controls.Handlers.Items
 return args;
 }
 
+protected override void UpdateEmptyViewVisibility()
+{
+if (_updatingEmptyView)
+{
+base.UpdateEmptyViewVisibility();
+return;
+}
+_updatingEmptyView = true;
+try
+{
+if (_loopableCollectionView is not null && ItemsView?.Loop == true)
+{
+bool isEmpty = (CollectionViewSource?.View?.Count ?? 0) == 0;
+_loopableCollectionView.IsLoopingEnabled = !isEmpty;
+if (isEmpty && ListViewBase.ItemsSource is not null)
+{
+ListViewBase.ItemsSource = null;
+}
+else if (!isEmpty && ListViewBase.ItemsSource is null)
+{
+ListViewBase.ItemsSource = _loopableCollectionView;
+}
+}
+base.UpdateEmptyViewVisibility();
+}
+finally
+{
+_updatingEmptyView = false;
+}
+}
+
 ListViewBase CreateCarouselListLayout(ItemsLayoutOrientation layoutOrientation)
 {
 UI.Xaml.Controls.ListView listView;
diff --git a/src/Controls/src/Core/Platform/Windows/CollectionView/LoopableCollectionView.cs b/src/Controls/src/Core/Platform/Windows/CollectionView/LoopableCollectionView.cs
index 1b84dd2f1f..c3928d374d 100644
--- a/src/Controls/src/Core/Platform/Windows/CollectionView/LoopableCollectionView.cs
+++ b/src/Controls/src/Core/Platform/Windows/CollectionView/LoopableCollectionView.cs
@@ -38,7 +38,7 @@ namespace Microsoft.Maui.Controls.Platform
 public int IndexOf(object item)
 {
- if (IsLoopingEnabled && CenterMode)
+ if (IsLoopingEnabled && CenterMode && _internal.Count > 0)
 {
 // The renderer will hit this on initial setup to move the ListView into the
 // "middle" of the giant set of totally fake items.
@@ -59,7 +59,7 @@ namespace Microsoft.Maui.Controls.Platform
 {
 get
 {
- if (!IsLoopingEnabled)
+ if (!IsLoopingEnabled || _internal.Count == 0)
 {
 return _internal.Count;
 }
@@ -194,7 +194,7 @@ namespace Microsoft.Maui.Controls.Platform
 void OnItemsVectorChanged(IObservableVector<object> sender, IVectorChangedEventArgs e)
 {
- _vectorChanged.Invoke(sender, e);
+ _vectorChanged?.Invoke(sender, e);
 }
diff --git a/src/Controls/src/Core/PublicAPI/net-windows/PublicAPI.Unshipped.txt b/src/Controls/src/Core/PublicAPI/net-windows/PublicAPI.Unshipped.txt
index c88246042d..75e7379560 100644
--- a/src/Controls/src/Core/PublicAPI/net-windows/PublicAPI.Unshipped.txt
+++ b/src/Controls/src/Core/PublicAPI/net-windows/PublicAPI.Unshipped.txt
@@ -1,4 +1,5 @@
 #nullable enable
+override Microsoft.Maui.Controls.Handlers.Items.CarouselViewHandler.UpdateEmptyViewVisibility() -> void
 ~override Microsoft.Maui.Controls.Handlers.Items.CarouselViewHandler.ScrollTo(Microsoft.Maui.Controls.ScrollToRequestEventArgs args) -> System.Threading.Tasks.Task
 override Microsoft.Maui.Controls.Shapes.Shape.OnPropertyChanged(string? propertyName = null) -> void
 override Microsoft.Maui.Controls.GraphicsView.OnBindingContextChanged() -> void
diff --git a/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue7150.cs b/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue7150.cs
index 4641936aa8..abd699e8b1 100644
--- a/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue7150.cs
+++ b/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue7150.cs
@@ -1,4 +1,3 @@
-#if TEST_FAILS_ON_WINDOWS // Related issue for windows: https://github.com/dotnet/maui/issues/29245
 using NUnit.Framework;
 using UITest.Appium;
 using UITest.Core;
@@ -18,5 +17,4 @@ public class Issue7150 : _IssuesUITest
     App.Tap("FilterButton");
     VerifyScreenshot();
 }
-}
-#endif
+}

[Shalini-Ashokan]

🤖 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 is the only candidate that produced a passing test on Windows. It fixes the root cause at the LoopableCollectionView layer by making Count truthful when empty (returns 0 instead of FakeCount=655360), toggles IsLoopingEnabled and disconnects ItemsSource when empty, removes the #if TEST_FAILS_ON_WINDOWS test exclusion, and adds a null-safety fix for _vectorChanged?.Invoke. The PR's approach (ItemTemplate=null only) leaves 655360 phantom nodes in the UIA tree and cannot enable Windows test coverage.

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)

I tested all three AI-suggested alternative fixes. None of them resolve the issue.

[kubaflo]

/review -b feature/refactor-copilot-yml

[MauiBot]

Expert Review — 2 findings

See inline comments for details.