Issue 1547: Microsoft JScript runtime error in qtip
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by vraghuva...@gmail.com, Sep 23, 2012
I integrated FullCalendar into my web app and got stuck with a JSCript runtime error. To make sure there were no integration issues, I just downloaded CalendarSitev1.1 sample project and just modified the eventDAO class to fill in dummy events. Getting same error. Totally stumped.

Error is: Microsoft JScript runtime error: Object doesn't support property or method 'isEmptyObject'

code in js around: a.isEmptyObject(h)&&(y.redraw(),d!==c&&y.reposition(G.event)

Occurs whenever we click or hover on events (events getting populated correctly).

Unable to attach anything to this bug as I see error "
Issue attachment storage quota exceeded"

This is the only blocking defect preventing my site launch. any help appreciated.
Sep 23, 2012
#1 vraghuva...@gmail.com
There was another runtime error regarding 'status'. I fixed the problem by modifying the qtip js file as below: added a null check to jquery.qtip-1.0.0-rc3.min.js

for (i = 0; i < f.fn.qtip.interfaces.length && null != f.fn.qtip.interfaces[i]; i++)

I see that f.fn.qtip.interfaces[i] is null for some values of i. no idea why? Anybody any insights?
Aug 18, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #3 adamrs...@gmail.com
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