| Issue 1714: | updateEvent fails with exception (used inside mouseover/mouseout) | |
| 2 people starred this issue and may be notified of changes. | Back to list |
code:
eventMouseover: (event, e) ->
event.color = '#0064CD'
$('#calendar').fullCalendar('updateEvent', event)
error: Uncaught TypeError: Cannot read property 'parentNode' of null
line: https://github.com/arshaw/fullcalendar/blob/master/src/util.js#L124
Mar 1, 2013
#1
sl.bug...@gmail.com
Apr 8, 2013
I am also facing the same issue.
Jun 19, 2013
Hi, I am also facing the same problem. Can you please tell me the solution for this?
Jul 2, 2013
I got it working using setTimeout and a boolean guard (otherwise eventMouseover will be called multiple times after each 'updateEvent'):
eventMouseover: function (event) {
if(event.colorUpdated) return;
event.backgroundColor = "#0064CD";
event.colorUpdated = true;
setTimeout(function() {
$('#calendar').fullCalendar('updateEvent', event);
}, 0);
}
- Regin
Aug 15, 2013
(No comment was entered for this change.)
Status:
ReproTemp
Aug 25, 2013
This message is being bulk-sent to a number of issues, both [very] old and new.
I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:
http://arshaw.com/fullcalendar/wiki/Report-a-Bug/
Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.
If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.
I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.
Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status:
Invalid
Labels: -Type-Defect Type-Bug |
|
| ► Sign in to add a comment |