| Issue 2225: | [beta] drop callback date doesn't have calendar's timezone | |
| 1 person starred this issue and may be notified of changes. | Back to list |
# You must follow these instructions when entering an issue: # # http://arshaw.com/fullcalendar/wiki/Report-a-Bug/ # http://arshaw.com/fullcalendar/wiki/Request-a-Feature/ # # Issues that do not follow these guidelines will be deleted without # explanation. # # Please erase this text and start typing :) in demo in beta1 drop: function(date) { // this function is called when drop at 9:00 am date.toDate() Date {Thu Aug 07 2014 05:00:00 GMT-0400 (Eastern Standard Time)} the date is UTC time 9:00am not local time 9:00am
Aug 6, 2014
#1
rik...@gmail.com
Aug 6, 2014
Issue on beta2
Aug 7, 2014
(No comment was entered for this change.)
Summary:
[skeleton] drop callback date is not correct
(was: drop callback date is not correct )
Status: Reproducing Labels: Type-Bug
Aug 14, 2014
(No comment was entered for this change.)
Summary:
[skeleton] drop callback date doesn't have calendar's timezone
(was: [skeleton] drop callback date is not correct )
Status: Accepted
Aug 14, 2014
(No comment was entered for this change.)
Summary:
[beta] drop callback date doesn't have calendar's timezone
(was: [skeleton] drop callback date doesn't have calendar's timezone)
Labels: milestone-skeleton
Aug 19, 2014
This issue has been fixed in the v2.1.0-beta3. http://blog.arshaw.com/1/post/2014/07/fullcalendar-210-beta.html I would greatly appreciate if you could verify this. Thanks!
Status:
Implemented
Aug 26, 2014
This issue has been resolved with the official release of v2.1.0: http://blog.arshaw.com/1/post/2014/08/fullcalendar-210-released.html Please post any follow-up bug reports or feature requests as separate issues. Thanks.
Status:
Released
|
|
| ► Sign in to add a comment |