Assess order/linking of binding subject

[guardrex]

Description

Per #35973 ...

With :get/:set binding, you can react to a value change before it's applied to the DOM, and you can change the applied value, if necessary. Whereas with @bind:event="{EVENT}" attribute binding, where the {EVENT} placeholder is a DOM event, you receive the notification after the DOM is updated, and there's no capacity to modify the applied value while binding.

Take a look and see about the ordering (is @bind:event="{EVENT}" covered before this?) ... either re-organize or cross-link coverage.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-10.0&preserve-view=true

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/data-binding.md

Document ID

3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc

Platform Id

ad2f661d-d520-a055-4a4e-26b9520e6ce3

Article author

@guardrex

Metadata

• ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
• PlatformId: ad2f661d-d520-a055-4a4e-26b9520e6ce3
• Service: aspnet-core
• Sub-service: blazor

Related Issues

[github-actions]

🏖️🌞 Summertime!! Woot!! 🏐⛵

Stand-by! ... A green dinosaur 🦖 will be along shortly to assist.

[georgehemmings]

The confusion for me is that even with @bind:set in place, the @bind:event still works alongside it. It's not an alternative like manually handling the DOM event would be.

<input type="text" @bind:get="text" @bind:set="Set" @bind:event="oninput" />