Details
-
Bug
-
Status: Reopened
-
Minor
-
Resolution: Unresolved
-
Adobe Flex SDK 3.4 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Browser: Firefox 3.x
Language Found: English
Description
The problem in its nutshell:
Currently DateField and DateFormatter share the single value specified in variable "dateFormat" in SharedResources.properties file, while those classes do not support the same set of formatting options (masks)
DateFormatter supports a full set of available formatting options (masks) see LiveDocs for "formatString":
http://livedocs.adobe.com/flex/3/langref/mx/formatters/DateFormatter.html#formatString
Y, M, D, E, A, J, H, K, L, N, S masks are supported
DateField supports only limited subset from full set of available formatting options(masks), see LiveDocs for "formatString"
http://livedocs.adobe.com/flex/3/langref/mx/controls/DateField.html#formatString
M, MM, D, YY, YYYY are supported, while even MMM and MMMM are not supported, probably bug: http://bugs.adobe.com/jira/browse/SDK-23075
E, A, J, H, K, L, N, S masks are not supported by DateField component
The problem is that anyone during localization process of "SharedResources.properties" can alter the value for "dateFormat" to include any masks from full subset of supported options for DateFormatter.
While this will be OK for Dates that are displayed with DateFormatter format applied, all Dates that are displayed in DateFields UI control will be screwed.
See attached Flex project sample that illustrates this problem.