[ https://issues.apache.org/jira/browse/FLEX-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217219#comment-13217219 ]
John Fletcher commented on FLEX-20: ----------------------------------- Haykel, I could give you some reasons, but I won't because I don't want to sidetrack since the question is out of scope of this issue. NaN is a supported feature in NumericStepper and actually works perfectly except when you attempt to replace it with a three-digit number. This issue is to commit a bugfix so that it works properly in all cases and that is what we should do here. Removing support for NaN in NumericStepper is a valid feature request which we could consider for the next version of Flex. If you want to open a new issue for that, please paste in the link here and I'll give you my thoughts over on that issue. > The Max value restriction in Spark NumericStepper doesn't work properly > ----------------------------------------------------------------------- > > Key: FLEX-20 > URL: https://issues.apache.org/jira/browse/FLEX-20 > Project: Apache Flex > Issue Type: Bug > Components: Project Management > Environment: Apache FlexSDK 4.6 - Adobe FlexSDK 4.6 - Adobe FlexSDK > 4.5 > Reporter: Pierangelo Mancusi > Assignee: Bertrand Delacretaz > Priority: Minor > Labels: patch > Attachments: NumericStepperPatch.txt > > > original issue: https://bugs.adobe.com/jira/browse/SDK-31123 > here a summary: > Steps to reproduce: > 1.Launch the browser with Numeric stepper. Set the min value as 10 max value > as 50. Also set default values as 20. > 2.After launching the broswer clear the default value 20 and focus out from > the numeric stepper. It displays "NAN" > 3. Again focus back to the numeric stepper and try to edit 3 digit value > (Eg.777). Then foucs out. It doen't restrict to max value i.e"50" as set > earlier in > step 1. It allows the 3 digit value enetered instead. > > Actual Results: The enetered value will be displayed > > > Expected Results: It should restrict and display the max values as set in > step 1. > > > Workaround (if any): No Work around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira