| Issue 2080: | 2.0 beta: fullCalendar's version of the moment constructor does not work with unix timestamps | |
| 1 person starred this issue and may be notified of changes. | Back to list |
In 2.0 beta, when I use the fullCalendar's version of the moment constructor with a unix timestamp as argument (instead of a string), I get a moment object with the browsers time zone instead of an "ambiguously-timed" one.
Both versions of the constructor should return an ambiguously-timed object.
I pasted this from the java script console:
> $.fullCalendar.moment('2012-03-03')
< e
_a: Array[7]
_ambigTime: true
_ambigZone: true
_d: Sat Mar 03 2012 01:00:00 GMT+0100 (CET)
_f: "YYYY-MM-DD "
_fc: true
_i: "2012-03-03"
_isUTC: true
_l: undefined
_offset: 0
_pf: Object
_strict: undefined
_useUTC: true
__proto__: e
> $.fullCalendar.moment(76543)
< e
_d: Thu Jan 01 1970 01:01:16 GMT+0100 (CET)
_f: undefined
_fc: true
_i: 76543
_isUTC: false
_l: undefined
_pf: Object
_strict: undefined
__proto__: e
Jan 30, 2014
Project Member
#1
adamrs...@gmail.com
Status:
WontFix
|
|
| ► Sign in to add a comment |