flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Fletcher (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-20) The Max value restriction in Spark NumericStepper doesn't work properly
Date Mon, 27 Feb 2012 09:53:48 GMT

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

John Fletcher commented on FLEX-20:

Pierangelo, I've had a look at your patch and I'm glad to see someone is working on this,
but I believe that this is not the correct solution to the problem. Your solution is effectively
to prohibit NaN from being allowed in NumericSteppers. Currently NaN is permitted, so this
patch would constitute a design change with further reaching consequences, not a simple bug

Have you read my comment at https://bugs.adobe.com/jira/browse/SDK-31123? This details what
I believe is a better solution.
> 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


View raw message