ExtJS's date formatter appears to be broken: 'time', 'timestamp', and 'u' all return invalid values. ('time' and 'timestamp' produce an - incomprehensible - alphanumeric string, and 'u' seems to produce "000" reliably.
Steps to reproduce the problem:
Get a submit value from a datefield with submitFormat specified. (datefield.getSubmitValue())
The result that was expected:
A valid time, timestamp, or millisecond representation of the date.
The result that occurs instead:
An invalid time, timestamp, or millisecond representation of the date.
Hmm - I was using them in my model. (not directly in a date picker - which was just the easiest way to demonstrate this.)
Is it possible the model's dateFormat configuration was using more than Ext.Date at one point? I know there are vestiges of the dateFormat config taking "time" and "timestamp" on the Ext.data.Field class according to the docs.
I can reproduce the problem.
I set dateFormat in the model to "time", and the server send a millisecond.
It's work correctily, but if I want to save this field the date format generate: '313710e' string
I thin it's parse the text char-by-char...
t - days in month (oct have 31)
i - minutes with leading zero (37)
m - month with leading zero (10)
e - 'e' becuase it's not parsed...