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

K Vikas Chandran edited comment on FLEX-33288 at 12/7/12 6:59 PM:
------------------------------------------------------------------

hi Gordon, customer has a business requirement which requires him to set it to 
NAN, if now a user explicitly sets any other number say 101[user input], it 
should allow it , should it not. 
                
      was (Author: chandran):
    hi Gordon, customer has a business requirement which requires him to set it 
to NAN, if now a user explicitly sets any other number say 101[user input], it 
should allow it , should it not.
                  
> Numeric Stepper value once NaN does not change to any number user sets or 
> increments
> ------------------------------------------------------------------------------------
>
>                 Key: FLEX-33288
>                 URL: https://issues.apache.org/jira/browse/FLEX-33288
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: NumericStepper
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: all
>            Reporter: K Vikas Chandran
>            Priority: Minor
>              Labels: NaN, numeric, numericstepper, stepper
>             Fix For: Adobe Flex SDK 4.6 (Release)
>
>         Attachments: SampleFromClient.mxml, workAround.mxml
>
>
> Problem: Numeric Stepper value once NaN does not change to any number user 
> sets or increments
> Method: 
> -Run sample application "SampleFromClient.mxml"
> -Click the button "Set Value to 'Nan'"
> -set the value to some other value say 101 [any 100-999]
> -Click the numeric stepper to increment or decrement the value.
> Result:
> The text on the Numeric stepper remains 'NaN'
> Expected:
> Should change an increment w.r.t the input value
> Workaround:
> Crude please refer  "workaround.mxml"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to