[inflight regression][iOS/macOS] Fix CollectionView, RefreshView, and ScrollView interaction state after IsEnabled toggles

[SyedAbdulAzeemSF4852]

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 iOS and macOS, four tests — CollectionViewScrollsWhenRefreshViewDisabled, ScrollViewInitiallyNotEnabledThenEnabled, ProgressSpinnerWorksWhenReEnabled, and VerifyCollectionViewIsEnableState — are failing in candidate PR July 13th, Candidate #36411 due to PR [iOS] Respect InputTransparent when updating UserInteractionEnabled #36305.

Root Cause

• PR [iOS] Respect InputTransparent when updating UserInteractionEnabled #36305 updated ViewExtensions.UpdateIsEnabled to compute UserInteractionEnabled using both IsEnabled and InputTransparent for non-UIControl views. However, because CollectionView, RefreshView, and ScrollView override MapIsEnabled without invoking the shared implementation, they never adopted this new logic, causing inconsistent UserInteractionEnabled behavior across enable/disable state changes and resulting in failures in CollectionViewScrollsWhenRefreshViewDisabled, ProgressSpinnerWorksWhenReEnabled, VerifyCollectionViewIsEnableState, and ScrollViewInitiallyNotEnabledThenEnabled.

Description of Change

• Introduced a new UpdateInteractionState extension method in ViewExtensions.cs that centralizes the logic for setting UserInteractionEnabled based on both IsEnabled and InputTransparent, and updated both UpdateIsEnabled and UpdateInputTransparent to use this method.
• Updated MapIsEnabled methods in handlers for ItemsViewHandler, ItemsViewHandler2, RefreshViewHandler, and ScrollViewHandler to call the base ViewHandler.MapIsEnabled, ensuring interaction state is always recomputed.

Issues Fixed

Fixes #36501

Validated the behaviour in the following platforms

• Windows
• Android
• iOS
• Mac

Output

TestCase	Before	After
CollectionViewScrollsWhenRefreshViewDisabled
ScrollViewInitiallyNotEnabledThenEnabled
ProgressSpinnerWorksWhenReEnabled
VerifyCollectionViewIsEnableState

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

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

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[sheiksyedm]

/azp run maui-pr-uitests , maui-pr-devicetests

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[github-actions]

Tests Failure Analysis

@kubaflo — test-failure review results are available based on commit 0ae7593.

Maintainers can request a fresh review after new comments, commits, or CI runs by commenting /review tests.

Test Failure Review: Needs human investigation - click to expand

Overall verdict: Needs human investigation. Zero of the 190 distinct failures are provable regressions against the base branch (inflight/candidate, 5 recent builds sampled per pipeline), and 17 also appear on base — but every failure resolved as indeterminate (leg-only base matches, not exact test+platform matches), so none can be dismissed as pre-existing. Combined with 117 build legs that produced no extractable failure, 2 UITest checks that did not finish cleanly, and 3 device-test checks whose clean result could not be confirmed, the failures cannot be safely attributed either way and require a human to classify.

• i Uncertain — Unexplained / aborted / unverified CI legs (~122 legs): 117 failed build legs yielded no extractable failure (crossgen/NativeAOT/linker/integration-test breaks across Blazor, AOT, RunOniOS, WindowsTemplates), 2 macOS UITest checks did not finish cleanly (cancelled/timed-out), and 3 device-test checks read green but XHarness Failed==0 could not be confirmed.
• i Uncertain — Android SDK provisioning failures (~16 legs): avdmanager/Failed to find package 'platform-tools;35.0.2' also fails across all 5 sampled base builds but only as a leg match, so it is not dismissible; e.g. to find package 'platform-tools;35.0.2'.
• i Uncertain — iOS Flyout measurement failures (~96 tests): FlyoutHeaderContentAndFooterAllMeasureCorrectly reports a consistent 34px footer-Y offset (Expected: 761. Actual: 795); this touches the ScrollView/iOS layout area this PR modifies, so it warrants a human look even though it is not a proven base regression.
• i Uncertain — Shadow-transform NullReferenceExceptions (~11 tests): the Verify*AndShadow family throws NullReferenceException and also fails on base (leg match only), so not dismissible; e.g. VerifyScaleXAndShadow.
• i Uncertain — Device-test failures & incomplete work items (~8 tests): gesture leak tests, ItemsUpdateWithCollectionChanges, a crashed Helix work item, and GroupedCollectionViewGridLayoutRendersCorrectly (missing baseline snapshot) — all indeterminate.
• i Uncertain — Build/publish errors (~6 legs): PublishTestResults, DeviceTests*(Windows), and mac UITest result-publish steps exited non-zero with no test-level cause.

Coverage: 175 checks · 105 passing · 70 failing · 0 pending · 0 inaccessible · 2 unmapped · 117 unexplained build legs · 0 unaccounted failing checks · 2 aborted failing checks · 0 canceled-build checks · 3 device-test unverified · 190 unattributed · 0 regressed-vs-base. Deterministic ceiling: Needs human investigation — 2 unmapped checks, 117 unexplained legs, 2 aborted UITest checks, 3 unverified device-test checks, and 190 unattributed failures.

Builds (this PR): maui-pr 1524976, maui-pr-devicetests 1524978, maui-pr-uitests 1524977. Base sampling (inflight/candidate, 5 recent builds per definition): maui-pr 1521712, maui-pr-devicetests 1521714, maui-pr-uitests 1521713.

Recommended action

A maintainer should manually confirm CI health: the base branch (inflight/candidate) is itself red, so re-run the failed legs and confirm whether the ~96 iOS FlyoutHeaderContentAndFooterAllMeasureCorrectly measurement failures are related to this PR's ScrollView/iOS layout changes before merging.

Visual failure comparisons

Full-resolution CI baseline, actual, and diff images are embedded below. They supplement the failure classification and do not change the deterministic verdict ceiling.
Relationship labels use deterministic exact test-and-platform baseline evidence plus exact changed snapshot/test scope; missing or mixed evidence remains Needs human investigation.

Visual comparisons were prepared but could not be published to the asset branch because a Git or API error occurred after image preparation. The deterministic verdict is unaffected; no images are shown for this run.

4 additional visual comparison(s) were omitted by publisher bounds (deduplication, the comparison cap, the discovery/publish time budget, or assets that failed validation).