Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Mon, 27 Feb 2012 10:01:49 +0000 (UTC)
From: "Haykel Ben Jemia (Commented) (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: 
 <411958535.22678.1330336909266.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <912928068.19888.1330195908492.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (FLEX-20) The Max value restriction in Spark
 NumericStepper doesn't work properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FLEX-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217135#comment-13217135 ] 

Haykel Ben Jemia commented on FLEX-20:
--------------------------------------

Why should the numeric stepper allow for NaN? IMHO it should only allow numbers to be entered, is there a reason for allowing NaN?
                
> 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