| Issue 1303: | Trigger eventResizeStop after event has been updated | |
| 1 person starred this issue and may be notified of changes. | Back to list |
When using eventResizeStop() in FullCalendar 1.5.3 the event end date is still set to the value it began with when resizing began. Moving the call to trigger, in the stop callback for function resizableSlotEvent() (Line 4187), to the end of the function (Line 4194) appears to rectify the issue. I do not know if this modification causes any regression issues.
Mar 13, 2013
#1
mathi...@4nkh.com
Aug 15, 2013
(No comment was entered for this change.)
Summary:
Trigger eventResizeStop after event has been updated.
(was: eventResizeStop is called before event object is updated, causing wrong date when submitting to server)
Status: Discussing Labels: -Type-Defect Type-Behavior
Apr 19, 2015
(No comment was entered for this change.)
Summary:
Trigger eventResizeStop after event has been updated
(was: Trigger eventResizeStop after event has been updated.)
Labels: -Type-Behavior Type-Feature
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/1570 This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event. Happy coding, Adam
Status:
ExportedToGithub
|
|
| ► Sign in to add a comment |