@bind:event not working on input element

[SteveSandersonMS]

I thought the following would work:

<input @bind="@someText" @bind:event="oninput" />

... but it does not (it only updates on change, not on input).

To update on each keystroke, you have to use the following less obvious syntax instead:

<input @bind-value="@someText" @bind-value:event="oninput" />

Also I think we should dropon from these event names, as it feels less obvious than @bind:event="input". The on prefix is a bit of a historical oddity in HTML/JS generally, e.g., more recent APIs like addEventListener don't use on prefixes for event types.

[danroth27]

I expected <input @bind="someText" @bind:event="oninput" /> to work (see #10909)

[ajaybhargavb]

To add more info, this is not a regression. This just was never supported.
In the past we could either do <input bind="someText" /> or <input bind-value-oninput="someText" />. There was no way to infer the value part but specify the event.

[rynowak]

Not a regression, but we should support it 👍 This was in some of the examples and design notes, but I don't think it showed up in the issue's checklist of stuff.

[ajaybhargavb]

I started working on this but I realized supporting this goes against our current design,
Consider,

    [BindElement(""div"", ""value"", ""myvalue"", ""myevent"")]
    public static class BindAttributes
    {
    }

<div @bind-value=""ParentValue"" />
This gets resolved as follows,
valueAttributeName = myvalue
changeAttributeName = myevent

Now if we add a @bind:event attribute,

<div @bind-value=""ParentValue"" @bind-value:event=""anotherevent"" />
Should it now resolve to,
valueAttributeName = myvalue
changeAttributeName = anotherevent
?

Supporting that goes against the intended design as mentioned in the comment here.

@SteveSandersonMS @rynowak can you clarify more on the requirements? Also the change in design works with custom BindAttributes specifications?

[ajaybhargavb]

I have a PR with changes that make sense to me.