[
https://issues.apache.org/jira/browse/TOBAGO-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-2071.
-------------------------------------
Resolution: Fixed
> Changes for <tc:date>
> ---------------------
>
> Key: TOBAGO-2071
> URL: https://issues.apache.org/jira/browse/TOBAGO-2071
> Project: MyFaces Tobago
> Issue Type: Task
> Components: Core, Themes
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Priority: Major
> Fix For: 5.0.0
>
>
> h3. Changes
> We need some changes to the <tc:date> component.
> * Implement "more like HTML"
> * No longer use for <f:convertDateTime> - ({color:#de350b}Todo/TBD{color}:
> support for this converter might be possible in some cases)
> h3. Explanation
> The input of date and time is nomally supported by the browser (for quite all
> browsers, even for mobile devices) or as an alternative as JavaScript widget.
> So, the value "on the wire" will be a machine readable ISO format, not a
> localized value. The localization will happen in the browser. This is defined
> in the specification of input type="date" etc.
> h3. Exclusion
> For <tc:in> the <f:dateTimeConverter> should work, but without widget support.
> h3. Type
> There will be an attribute "type" = \{ "date" | "time" | "datetime-local" |
> "month" | "week" }
>
> ||class of value||converter||type||pattern||html||
> |java.util.Date|<auto>| | |<input type="datetime-local">|
> |java.time.LocalDate|<auto>| | |<input type="date">|
> |...| | | | |
>
>
> (Month and week may be supported in later versions)
> h3. Browser vs Widget
> Most browsers these days supporting the types "date" and "time". Firefox
> doesn't support "datetime-local". So, it might be a solution, to use only
> browser featues. In case of Firefox with "datetime-local", the field may be
> splitted into 2 fields with type "date" and "time".
> If everything works fine, we may drop TOBAGO-2036.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
