MudEventManager: Correctly handle TouchList properties in touch-related events#10714
Conversation
|
And Firefox partially supported. |
|
Sorry for the mistake. I was thinking: since |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #10714 +/- ##
==========================================
- Coverage 91.84% 91.83% -0.01%
==========================================
Files 427 427
Lines 13428 13428
Branches 2591 2591
==========================================
- Hits 12333 12332 -1
Misses 523 523
- Partials 572 573 +1 ☔ View full report in Codecov by Sentry. |
|
Funny how AI gives different results to caniuse. |
|
That's why IMO AI is overhyped ATM because you can't trust it. People are slowly discovering that you need to check everything it produces, so it isn't really useful for automation. |
|
Thanks @pwasilewski ! |





Description
This update improves the event handler to correctly handle
TouchListproperties in touch-related events. TheTouchList, a specialized collection of touch points (e.g., for multitouch), is now converted into a standard array of objects. Each touch point is transformed into a plain object with properties such asidentifier,screenX,screenY,clientX,clientY,pageX, andpageY, making it suitable for JSON serialization (as per ASP.Net Core TouchPoint documentation).This is especially important for ASP.Net scenarios, where the
TouchListcannot be directly serialized into a format that the framework can process. The transformation ensures that the touch points are sent as an array of objects (TouchPoint[]), which can be properly deserialized (as per ASP.Net Core TouchEventArgs documentation).fix #10632
How Has This Been Tested?
Visually
Type of Changes
Checklist
dev).