[
https://issues.apache.org/jira/browse/FLEX-35106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362498#comment-15362498
]
Peter Marcoen commented on FLEX-35106:
--------------------------------------
[~jmclean] I think it's an overuse of the parseFunction (by default
stringToDate).
The parseFunction gets called in:
# set date: when the value is a string
# displayDropdown
# focusOutHandler
# keyDownHandler: when the key pressed is ENTER
# textInput_changeHandler
I see the value of calling it in the textInput_changeHandler, but in the other
functions it might not be needed? If the text field is updated manually it has
to trigger textInput_changeHandler.
> Incorrect date in datefield popup for fr_FR locale
> --------------------------------------------------
>
> Key: FLEX-35106
> URL: https://issues.apache.org/jira/browse/FLEX-35106
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: DateField
> Affects Versions: Apache Flex 4.15.0
> Environment: Windows 7
> Reporter: Peter Marcoen
> Assignee: Justin Mclean
> Labels: datefield, french, locale
>
> h4. Steps to reproduce:
> 1. Create a new project
> 2. Set the compiler arguments to "-locale fr_FR"
> 3. Add the following line to the main application:
> {code:xml}
> <mx:DateField selectedDate="{new Date(2016, 6, 4, 13)}"/>
> {code}
> 4. Run the application and click on the calendar icon
> h4. Expected result:
> The selected date should be the 4th of JULY, which it is if you set the
> locale to "en_US"
> h4. Actual result:
> The selected date is the 4th of JUNE
> h4. Possible reason:
> Because the abbreviation of june and july is the same in French ("Jui"), the
> popup probably finds the first month who's abbreviated name matches the
> selected abbreviated name and thus incorrectly sets the month to June
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
