Sean Overman
Top achievements
Rank 1
Rank 1
Sean Overman
asked on 26 Aug 2009, 11:06 PM
I have a RadNumericTextBox with AutoPostBack set to true, and server side event attached to the TextChanged event.
I'm using spinners, and setting the MaxValue dynamically on the server side. When I attempt to change the value of the box past the MaxValue, the control validates and places the warning symbol correctly, however it still produces a generic postback. How can I stop this postback from happening, since no data has changed on the front end. Is there a client event that I can attach to and cancel if an attempt is made to go past the max value?
It should also be noted that the same "generic" postback happens if you try to spin below the minvalue as well, or manually attempt to enter a invalid value. However, keying invalid characters, ie (non-numeric) raises the validation icon, but does not cause a postback.
Thanks
I'm using spinners, and setting the MaxValue dynamically on the server side. When I attempt to change the value of the box past the MaxValue, the control validates and places the warning symbol correctly, however it still produces a generic postback. How can I stop this postback from happening, since no data has changed on the front end. Is there a client event that I can attach to and cancel if an attempt is made to go past the max value?
It should also be noted that the same "generic" postback happens if you try to spin below the minvalue as well, or manually attempt to enter a invalid value. However, keying invalid characters, ie (non-numeric) raises the validation icon, but does not cause a postback.
Thanks
1 Answer, 1 is accepted
0
Hi Sean Overman,
I successfully reproduced the described behavior. Indeed, this is unexpected and will be fixed for our next release. You can also download and use one of our next internal builds, which will also have this bug resolved.
If you download the latest official version of RadControls (Q2 2009 SP1, released yesterday), you can workaround the problem by setting the new property AllowOutOfRangeAutoCorrect to "false". In next version this workaround will not be necessary.
Sorry for the inconvenience. I have updated your Telerik points for bringing the issue to our attention.
Best wishes,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
I successfully reproduced the described behavior. Indeed, this is unexpected and will be fixed for our next release. You can also download and use one of our next internal builds, which will also have this bug resolved.
If you download the latest official version of RadControls (Q2 2009 SP1, released yesterday), you can workaround the problem by setting the new property AllowOutOfRangeAutoCorrect to "false". In next version this workaround will not be necessary.
Sorry for the inconvenience. I have updated your Telerik points for bringing the issue to our attention.
Best wishes,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.