Click
and DoubleClick
should directly use MouseEventArgs
#617
Milestone
Click
and DoubleClick
should directly use MouseEventArgs
#617
Current Situation
The current state offers multiple overloads with a dozen of properties which are mapped one to one to the
MouseEventArgs
:The motivation behind is to have a "valid" argument passed down which behaves like Blazor would in a "real" scenario (
detail = 1
for example forClick
anddetail = 2
forDoubleClick
).Proposed Solution
bUnit already offers an overload which takes the
MouseEventArgs
. This decouples bUnit from the supported .NET versions. For example in .net5OffsetX
andOffsetY
was introduced. In .net6PageX
andPageY
was introduced. Thus this "simple" version just works.Furthermore the suggestion would be to delete
Click
andDoubleClick
with all it's overloads and just offer 2 versions:In any way a small migration guide should be added to the docs.
Advantages:
ClickAsync
which is also public does use theMouseEventArgs
. That seems a bit in-cohesive as well. Normal expectation is that the sync and async version have the same parameter (except maybeCancellationToken
or similar stuff)Disadvantages:
The text was updated successfully, but these errors were encountered: