Skip to content
This repository has been archived by the owner on Feb 25, 2021. It is now read-only.

Marshal oninput events as UIChangeEventArgs #1673

Merged
merged 3 commits into from
Nov 13, 2018

Conversation

SteveSandersonMS
Copy link
Member

Same as #1475

Sebastian Reinhard and others added 2 commits November 13, 2018 13:06
- Blazor does handle the oninput event, but it is marshalled as a regular UIEventArgs
- This means that we cannot access the new value of the input element from inside our oninput handler

Addresses #821
@SteveSandersonMS SteveSandersonMS merged commit 6527637 into master Nov 13, 2018
@SteveSandersonMS SteveSandersonMS deleted the stevesa/fix-oninput branch November 13, 2018 13:40
@SteveSandersonMS SteveSandersonMS added bug and removed bug labels Nov 13, 2018
SteveSandersonMS added a commit to SteveSandersonMS/BlazorMigration that referenced this pull request Nov 27, 2018
* Marshal oninput events as UIChangeEventArgs

- Blazor does handle the oninput event, but it is marshalled as a regular UIEventArgs
- This means that we cannot access the new value of the input element from inside our oninput handler

Addresses #821
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants