Replace mouse events with pointer events in applicable components

[danielchalmers]

Description

Naturally supports mouse, touch, and pen (among other) inputs uniformly which improves accessibility and should be preferred for modern applications.

All functionality should be the same for existing mice users

Migration Guide:

• TableRowHoverEventArgs and Table methods now accept PointerEventArgs instead of MouseEventArgs

How Has This Been Tested?

unit, visually

Type of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (fix or improvement to the website or code docs)

Checklist

• The PR is submitted to the correct branch (dev).
• My code follows the code style of this project.
• I've added relevant tests.

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 90.49%. Comparing base (28bc599) to head (70688ce).
Report is 214 commits behind head on dev.

Files	Patch %	Lines
...c/MudBlazor/Components/Tooltip/MudTooltip.razor.cs	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #8974      +/-   ##
==========================================
+ Coverage   89.82%   90.49%   +0.66%     
==========================================
  Files         412      394      -18     
  Lines       11878    12139     +261     
  Branches     2364     2369       +5     
==========================================
+ Hits        10670    10985     +315     
+ Misses        681      621      -60     
- Partials      527      533       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielchalmers]

@henon @ScarletKuro Could I get a bit of help testing the Table and DataGrid? Don't think the resizer is working but I never use those two controls 🤷

[Anu6is]

Renamed MouseEvent.MouseOver -> HoverOver

Shouldn't it just be Hover?

[henon]

MouseOver is already the perfect name, I'm against renaming it.

[henon]

@henon @ScarletKuro Could I get a bit of help testing the Table and DataGrid? Don't think the resizer is working but I never use those two controls 🤷

Could you compare against v6 behavior to see if something broke.

[danielchalmers]

MouseOver is already the perfect name, I'm against renaming it.

@henon PointerOver?

EDIT: @Anu6is because it's the event from the pointer being over, not exclusively the mouse. but i think Hover is also good

[henon]

Touch can not hover only Mouse can, that's why I think MouseOver is still a good name.

[danielchalmers]

Touch can not hover only Mouse can, that's why I think MouseOver is still a good name.

@henon don't forget pens, etc

[henon]

OK let's do PointerOver

[danielchalmers]

Tests pass and I've manually checked and all seems the same with mouse. This will help with accessibility.

[ScarletKuro]

I think it would be nice to merge #8972 before this.

[danielchalmers]

I think it would be nice to merge #8972 before this.

@ScarletKuro Do you mind fixing the conflict for me? Or i can do it when i get home nbd

[ScarletKuro]

@ScarletKuro Do you mind fixing the conflict for me? Or i can do it when i get home nbd

Idm, but I will do it tmr in that case, it's pretty late for me now.

[ScarletKuro]

@ScarletKuro Do you mind fixing the conflict for me?

Done

[danielchalmers]

@henon Should be good now

[henon]

Migration Guide:

• MouseEvent.MouseOver -> PointerOver
• MouseEvent -> PointerEvent
• OnRowMouseEnter -> OnRowPointerEnter
• OnRowMouseLeave -> OnRowPointerLeave

I am not sure about the renames. I feel like I'd rather leave the names all the same including the MouseEvent enum. Supporting pens and touch devices is one thing but renaming everything is quite unnecessary. And I feel it doesn't make the API so much better that it is justified.

[danielchalmers]

I am not sure about the renames. I feel like I'd rather leave the names all the same including the MouseEvent enum. Supporting pens and touch devices is one thing but renaming everything is quite unnecessary. And I feel it doesn't make the API so much better that it is justified.

It's a good point, either way is fine. Let me know and I'll change them back. @henon

[danielchalmers]

@henon Public API is now back to *Mouse*

[henon]

Thanks!

Added to v7.0.0 Migration Guide #8447