| Issue 2048: | eventDrop gives incorrect minuteDelta when dragging an allDay event to a specific time if it has previously been an allDay event | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Dragging an allDay event down to a specific time gives the correct minuteDelta information. But, if that event is subsequently dragged back to an allDay event and then dragged back down to a specific time again, the minuteDelta will be incorrect. To reproduce this: 1. Browse to http://jsfiddle.net/FnsGT/ (a fork of the template provided at the fullCalendar support pages, with some popups added). 2. Select the day or week view. 3. Select any allDay object and drag to 1am 4. The js popup will tell you correctly that the minuteDelta is 60 5. Drag the event back from 1am to allDay 6. The js popup will tell you that the minuteDelta is 0 7. Drag the event back down to 1am again 8. This time the minuteDelta will be 0 (not 60)
Dec 10, 2013
#1
diagne...@googlemail.com
Dec 11, 2013
tested on Firefox 19.0.2, Chrome 25.0.1364.172 m
Jun 7, 2014
(No comment was entered for this change.)
Status:
Reproducing
Labels: Type-Bug
Jun 11, 2014
in version 2.0.0 i left the delta parameter out, but in 2.0.1 i'm reintroducing it. anyway, that part of the code was completely refactored in v2 and producing the correct outcome. when 2.0.1 is released you will see that it works. https://github.com/arshaw/fullcalendar/commit/957635adfcd8d0b742b15a200bb7f8fdfdfedf80
Status:
Implemented
Jun 15, 2014
v2.0.1 has been released. the `delta` argument should be accurate.
Status:
Released
|
|
| ► Sign in to add a comment |