Not setting event type by default

[egil]

In the latest version of Blazor E2E tests, the KeyPressEventComponent expects the event onkeypress to be listed as keypress in KeyboardEventArgs.Type.

I think bUnit should set it automatically for the user in the EventDispatchExtensions methods, unless the user explicitly provides a different value.

Thoughts?

[linkdotnet]

Hmm given that it is deprecated and type seems to be always "keypress", we wouldn't bother anyone with the changed logic.

I am really neutral on this one, as I don't see any harm but also not much gain :D

[egil]

Interesting. My approach is more that we should be consistent with what Blazor does "in production", even if that's not how things are supposed to be.

But I guess this is more a "figure out what Blazor does" assignment in the first place.

[linkdotnet]

Interesting. My approach is more that we should be consistent with what Blazor does "in production", even if that's not how things are supposed to be.

But I guess this is more a "figure out what Blazor does" assignment in the first place.

Is this something Blazor does or the Browser?

[egil]

Interesting. My approach is more that we should be consistent with what Blazor does "in production", even if that's not how things are supposed to be.

But I guess this is more a "figure out what Blazor does" assignment in the first place.

Is this something Blazor does or the Browser?

Their e2e would blow up if they didn't, so I assume so.