RangeSelector isn't usable with touch

[dongle-the-gadget]

Describe the bug

Users can't hold the thumbs of the RangeSelector, making the touch experience very bad.

Steps to reproduce

Reproducible in the Sample App (in the Store):
1. Go to the RangeSelector sample page.
2. Hold on one of the circular thumbs and try to drag them.
3. Notice that they won't change their values.

Expected behavior

It should be possible to change the range by dragging using touch.

Screenshots

No response

Code Platform

• [X] UWP
• [ ] WinAppSDK / WinUI 3
• [ ] Web Assembly (WASM)
• [ ] Android
• [ ] iOS
• [ ] MacOS
• [ ] Linux / GTK

Windows Build Number

• [ ] Windows 10 1809 (Build 17763)
• [ ] Windows 10 1903 (Build 18362)
• [ ] Windows 10 1909 (Build 18363)
• [ ] Windows 10 2004 (Build 19041)
• [ ] Windows 10 20H2 (Build 19042)
• [ ] Windows 10 21H1 (Build 19043)
• [ ] Windows 10 21H2 (Build 19044)
• [ ] Windows 10 22H2 (Build 19045)
• [ ] Windows 11 21H2 (Build 22000)
• [X] Other (specify)

Other Windows Build number

27686

App minimum and target SDK version

• [ ] Windows 10, version 1809 (Build 17763)
• [ ] Windows 10, version 1903 (Build 18362)
• [ ] Windows 10, version 1909 (Build 18363)
• [ ] Windows 10, version 2004 (Build 19041)
• [ ] Windows 10, version 2104 (Build 20348)
• [ ] Windows 11, version 22H2 (Build 22000)
• [ ] Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

Desktop

Additional context

No response

Help us help you

No, I'm unable to contribute a solution.

[Arlodotexe]

It didn't repro on my first check, but the second and subsequent checks (including the recording below) were able to reproduce the issue.

https://github.com/user-attachments/assets/74db41a4-52e9-435a-8ca9-14ff0fbda891

Tapping seems to work still:

https://github.com/user-attachments/assets/56581fc6-46df-4101-83d6-c6d83c4c43f5

Occasionally, dragging then moving the pointer to the stopping position will cause the thumb to follow the cursor until it leaves the RangeSelector.

It's not clear why these things are happening, we'll need to examine the code for clues.