Regression: Windows are always "inactive"

[Marv51]

Describe the bug

In WinAppSDK 1.6.1, I am unable to scroll any scroller control using mouse wheel if mouse option to scroll inactive windows is OFF.

This was reported as #8764 and fixed before, but now this is broken again. There are multiple people that experience this regression who commented in the original issue.

Steps to reproduce the bug

1. Go to Windows Mouse settings
2. Disable scroll of inactive windows on mouse over
3. Open a WinUI 3 app.
4. Nothing will scroll using mouse wheel, even if focused.

Expected behavior

The same that happens for any other software: scroll working when window is active.

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.6.1: 1.6.240923002

Windows version

Windows 11 (22H2): Build 22621

Additional context

I mostly copy and pasted this issue from the original report in #8764 from 2022, as it describes the issue well. But I am worried that comments on a closed issue are not getting the urgent attention that this regression needs.

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Closed similar issues:

• For Windows WinUI3 windows are always "inactive" (#8764), similarity score: 0.85
• When the Windows setting "Scroll inactive windows when hovering over them" is disabled, scrolling with the mouse is broken in WinUI3 app (#8161), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Marv51]

@hiteshkrmsft Can you clarify what version this was fixed in and if any developer steps are required?

My app built with the latest WinAppSDK 1.6.6 still reproduces this regression. The latest WinUI 3 Gallery version from the Store also shows this broken behavior.

[codendone]

@Marv51 Looking at the internal bug, the fix is in for the upcoming 1.7 release.

[codendone]

Oops, correction: There is intent to get it into 1.7, but the change is currently just in 1.8 with an open issue to bring it to 1.7.

[bogdan-patraucean]

There's multiple issues opened regarding this bug, please propritize it because it makes apps literally unusable.

@codendone some of use have hundreds of thousands of users..

https://github.com/microsoft/microsoft-ui-xaml/issues/10213

[svsnux]

Where can we download 1.8?. even if it is experimental. I need a solution urgently.

[bogdan-patraucean]

@svsnux there no 1.8 experimental at this time.

[svsnux]

@codendone any eta on fixed merged into 1.7 release? or 1.8 experimental 1

[codendone]

@svsnux The fix will be in the upcoming 1.8-experimental1 release. It is being evaluated for servicing to 1.7.

[bogdan-patraucean]

@codendone was this added to 1.7?

[agniuks]

@codendone was this added to 1.7?

The fix will be in the upcoming 1.7.5 release.