I have found two bugs associated with the RangeChangedScript in the Blazor Scatter Charts.
1) If you set the MaximumValue of the NumericXAxis, the RangeChangedScript will cease to work.
2) If you have a single razor page that uses different RangeChangeScripts depending on whether the x axis is using values or date, the first time you load the page the chart will render correctly. However the next you render the chart with a different RangeChangedScript the chart will only remember the first one it loaded. If you use shift refresh to clear the browser cache it will then render correctly.
This is a very serious bug, the scatter chart will not render reproducibly correct. I have attached a blazor project which demonstrates the two bugs.
RangeChangedScriptBugs.zip
Hello and thank you for contacting Infragistics. I am investigating your sample today and looking for a solution. When running your sample I get this error, where the ID changes every time. Is this part of the steps?
No, I wasn't getting that error