[
https://issues.apache.org/jira/browse/TRINIDAD-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539702
]
Yee-Wah Lee commented on TRINIDAD-797:
--------------------------------------
1. The client DateTimeConverter makes use of the LocaleElements_<locale>.js
file, but only the locale elements for the page are sent down. Hence, the
client converter's attempt to convert the Date into a String uses the wrong
locale data.
2 . Possibly because of this, the server code which generates the client
DateTimeConverter turns off client conversion, see
trinidad-internal\..\DateTimeConverter#getClientConversion() which returns null.
> Date-picker does not use the converter's locale attribute if it differs from
> page locale
> ----------------------------------------------------------------------------------------
>
> Key: TRINIDAD-797
> URL: https://issues.apache.org/jira/browse/TRINIDAD-797
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Reporter: Yee-Wah Lee
> Priority: Minor
>
> 1. Suppose the page locale is en_us. Add an inputDate to the jspx with a
> converter of a different locale, e.g.
> <tr:inputDate id="mdf6" value="#{date.date4}"
> label="attached converter">
> <tr:convertDateTime type="date" dateStyle="full"
> locale="fr_FR"/>
> </tr:inputDate>
> 2. Run the page - the inputDate shows up with the text in french, as expected.
> 3. Open the picker, and pick a different date.
> 4. When the picker closes, the inputDate has been updated with the Date in
> English.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
