Hello Philip,

To quote the article: "React onChange gets triggered on every keystroke on the keyboard." - this is when our ValueChanged event fires for all our inputs. We deliberately chose that to provide real-time updates, validation and experience, not just through an event, but also for two-way binding. For the range picker, that's two events: StartValueChanged and EndValueChanged.

Since these two events are also used for two-way binding by default, when you use them yourself to respond to user actions that quickly, you also have to do the upwards binding yourself, in Blazor you can't have both. You can read more about this here: Value Binding vs Data Binding.

Depending on what you are after, you may find the following two KB articles useful: Capture input keyboard events and OnChange fires twice.

As for what I see in the video - the app behavior will be extremely dependent on the code that is written around the components. I imagine that you would get that behavior if the grid data is bound to a .Where() clause that uses the dates from two-way binding, so that re-renders every time ValueChanged fires, but the chart is not (to change its data you need a specific event so you can update its data collection). So, a solution for that would be to either always use the ValueChanged events to update both components, or to use OnChange for both - not just the chart but also the grid.

Regards,
Marin Bratanov
Progress Telerik