🚧 Input Injection Test API Tests... #681
Draft
+118
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Toolkit Tracking issue: CommunityToolkit/Labs-Windows#176
Was initiative started with the initial Sizer controls when in Labs. Prior PR in Labs: CommunityToolkit/Labs-Windows#183
Also needs Tooling Branch: https://github.com/CommunityToolkit/Tooling-Windows-Submodule/tree/llama/input-injection-2025
TODO: More fluent API surface and figuring out how to do a Drag operation instead of just Click... 😅
API: https://learn.microsoft.com/en-us/uwp/api/windows.ui.input.preview.injection.inputinjector.initializetouchinjection
Other docs: https://learn.microsoft.com/en-us/windows/apps/design/input/input-injection
Still, as far as I see all the examples are simple clicks down/up and don't explain drag. 🥲 Doc issue: MicrosoftDocs/windows-dev-docs#3887