Open egil opened 2 years ago
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
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.
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?
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.
In the latest version of Blazor E2E tests, the KeyPressEventComponent expects the event
onkeypress
to be listed askeypress
inKeyboardEventArgs.Type
.I think bUnit should set it automatically for the user in the EventDispatchExtensions methods, unless the user explicitly provides a different value.
Thoughts?