fix(Skia): [WPF] Issue #7829 SynchronizationContext

[workgroupengineering]

GitHub Issue (If applicable): closes #7829

PR Type

What kind of change does this PR introduce?

• Bugfix

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[gitpod-io]

[workgroupengineering]

Can anyone review this PR?

[jeromelaban]

I've added this test, which matches what you've mentioned:

But it does not seem to reproduce fix the issue, can you validate on your end?

[workgroupengineering]

I've added this test, which matches what you've mentioned:

But it does not seem to reproduce fix the issue, can you validate on your end?

If run in test it works as expected but if run in Real Test APP the issue is present. I have tryed with 4.1.0-dev.461.

[jeromelaban]

It would be important to understand what's different in the sample app, it's supposed to behavior the same way. Can you add the test in the runtime tests and see what results you're getting ?

[workgroupengineering]

It would be important to understand what's different in the sample app, it's supposed to behavior the same way. Can you add the test in the runtime tests and see what results you're getting ?

I try.

How can I do to indicate that the test must be performed only in wpf?

I need to create a real WPF window and call event a via the window API.

[jeromelaban]

The test should theoretically work on all platforms, but if we need to limit it to Skia, we'll be able to. Can you add it and launch a build? We'll see how far it goes :)

[MartinZikmund]

@jeromelaban Is there some way to the test could avoid requiring separate runtime test project for WPF specifically 🤔 ? (it does not seem so based on the fact the test needs to access WpfHost, but it would be nicer to be able to avoid the additional project.

[jeromelaban]

@jeromelaban Is there some way to the test could avoid requiring separate runtime test project for WPF specifically 🤔 ? (it does not seem so based on the fact the test needs to access WpfHost, but it would be nicer to be able to avoid the additional project.

I don't think it's necessary at this point. The test that requires a window to validate, this feels like a too low-level replacement for a UI test engine that would do this in a generic way.

The solution to override the synchronization context for all event going out seems a bit too wide as well, particularly if it's about events going out of Uno's APIs, for which the entry point is known. Let's change those entry points for now to set the proper synchronization context. We can create a test that uses the new pointer injection to validate that we get the proper synchronization context out inside of uno pointer or generic input handlers.