[jira] [Commented] (FLEX-16656) DateField format string causes null value in selectedDate

["Justin Mclean (JIRA)" <ji...@apache.org>]

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

Justin Mclean commented on FLEX-16656:
--------------------------------------

Still an issue even with updated dateToString and stringToDate methods.
                
> DateField format string causes null value in selectedDate
> ---------------------------------------------------------
>
>                 Key: FLEX-16656
>                 URL: https://issues.apache.org/jira/browse/FLEX-16656
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: mx: DateField
>    Affects Versions: Adobe Flex SDK 3.1 (Release)
>         Environment: Affected OS(s): Mac
> Affected OS(s): Linux RedHat 4
> Browser: Safari
> Language Found: English
>            Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1.  Create a DateField with the following (or similar) MXML: <mx:DateField x="10" y="10" id="revisionDateChooser" formatString="MM/YYYY"/>
> 2.  Build and run, select a date in the popup, then use the flex builder variable inspector to inspect the selectedDate property of the DateField
> 3.
>  
>  Actual Results:
>  The date is formatted as expected, but when I try the access the selectedDate property, it is null.  If I remove the format string, or set it to something that includes the date, such as "MM/DD/YY," it functions correctly.  
>  
>  Expected Results:
>  I expected the DateField's selectedDate property to contain a Date object representing the selected date, no matter how it is being formatted for display
>  
>  Workaround (if any):
>  don't use a format string
> Note: I apologize if this is a duplicate report... when I tried searching for an existing it pulled up 160 results, I skimmed through them and looked at a coupe of promising ones, but did not see this bug.

--
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