[Android] Controls on previous Page still clickable after navigation

[morning4coffe-dev]

Current behavior

When a new Recommended app is created and the user navigates to a different page, the controls on the previous page remain clickable or interactive. This can result in unintended actions being triggered on the previous page, even though the user is no longer viewing it:

Screen.Recording.2024-08-11.142753.mp4

Expected behavior

No response

How to reproduce it (as minimally and precisely as possible)

1. Create a new Recommended app
2. Navigate in the app
3. Click on the space where the button is on the previous page

Workaround

No response

Works on UWP/WinUI

Yes

Environment

No response

NuGet package version(s)

"Uno.Sdk": "5.3.96" or "Uno.Sdk": "5.4.0-dev.180"

Affected platforms

Android
iOS? - not able to test

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[MartinZikmund]

The recommended template has

 Background="{ThemeResource $themeBackgroundBrush$}"

Which in case of Material becomes ThemeResource BackgroundBrush - does this brush exist in Material?

Not sure if relevant, but just seemed interesting

[jeromelaban]

/cc @kazo0

[kazo0]

@MartinZikmund yes BackgroundBrush should be a valid material brush

[MartinZikmund]

@jeromelaban According to investigation by @Youssef1313, pre-requisite to fixing this is #17645 - this one feels quite urgent though, as it could mean people will accidentally click and trigger operations on previous pages in navigation stack as things stand.

[Youssef1313]

To add a bit of into. This seems like a ContentControl/ContentPresenter bug. I have a PR to align ContentControl/ContentPresenter on Skia which is blocked on TemplatedParent. So, after TemplatedParent is merged I could try to get my PR to be for all platforms rather than Skia only

[Xiaoy312]

well tp is completed... so you may proceed with CC/CP

[morning4coffe-dev]

CC @MartinZikmund I think this should be prioritized now.