Bug in CSV with date / time converter

bugCSV

Client-side conversion / validation fails in most cases for f:convertDateTime and valid dates / times

PrimeFaces 4.x (current)

The client-side converter for f:convertDateTime uses $.datepicker.parseDate(format, value, settings).
The problem with $.datepicker.parseDate ist an exception when the format doesn't have days
(works as designed). E.g. try to parse $.datepicker.parseDate("mm/y", "11/16").
An exception will be raised. "mm/y" for datepicker is exactly the pattern "MM/yy" in
f:convertDateTime. Simple attach e.g. <f:convertDateTime pattern="MM/yy" timeZone="..."/>
to p:inputText and use CSV. The date will be always invalid.

The same is for only time. The pattern "HH:mm" can not be converted / validated by CVS.
Try $.datepicker.parseDate or $.datepicker.parseTime in the FF / Chrome console on any
PF page with calendar. A time in format "HH:mm" or "hh:mm" is always invalid by CSV.
That means we can not use <f:convertDateTime pattern="HH:mm" .../>

To overcome this issue I parse these formats manuelly without $.datepicker.parseDate
in an own client-side converter (tricky but works).
It also work with moment.js (http://momentjs.com) or similar libs.