[
https://issues.apache.org/jira/browse/TRINIDAD-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700695#action_12700695
]
Matthias Weßendorf commented on TRINIDAD-458:
---------------------------------------------
the right channel is the [email protected] list. By using a subject that
starts like [Trinidad]
Looking at the code of the renderer (ChooseDateRenderer)'s encodeAll(), I see
that it looks for the
current date, here:
...
long currTimeMillis = 0;
Object currTimeValue = bean.getProperty (_currTimeKey);
if (currTimeValue != null)
currTimeMillis = ((Date) currTimeValue).getTime();
else
currTimeMillis = System.currentTimeMillis();
...
generally the current behavior has pros and cons, I agree.
Perhaps we can find a proper solution on the dev list for handing this...
> Allow users to control the starting date of date picker
> -------------------------------------------------------
>
> Key: TRINIDAD-458
> URL: https://issues.apache.org/jira/browse/TRINIDAD-458
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Simon Lessard
> Priority: Minor
> Attachments: trunk_patch90.patch
>
>
> Currently, date picker init itself to the current date (unless there's a
> DateTimeRangeValidator preventing it). This can be useful, but also
> problematic when the date to be selected is decently old, like a birthdate
> for instance. A decent workaround would be to add an attribute on the
> component to fix the initial selected date of the date picker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
