jQuery UI Widgets Forums Grid jqxgrid

This topic contains 3 replies, has 2 voices, and was last updated by  apulcino 9 years, 5 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    jqxgrid Posts
  • jqxgrid #69205

    apulcino
    Participant

    Hi,

    I think I found a bug in jqxgrid.js (and jqx-all.js by extension). In the source code on line 8391 there is the line:

    mid = parseInt((min + max) / 2)

    The problem is the mid variable is never declared. This doesn’t seem to be a problem in many browsers, but it is a problem in at least IE8. I think the declaration can be included with the one for min on line 8384 (var min = 0, mid;) or the one for max on line 8389 (var max = collection.length, mid;).

    This is in v3.7.1 and goes back to at least v3.2.1.

    Just thought I’d pass it along.

    Thanks,
    Andrew

    jqxgrid #69207

    apulcino
    Participant

    It looks like this issue also occurs in jqxlistbox.js, on line 704.

    jqxgrid #69219

    Dimitar
    Participant

    Hi apulcino,

    jqxGrid and jqxListBox work fine on Internet Explorer 8. You can check this by testing the online demos. Please also do not share any portions of the source code, because this violates the jQWidgets End User License Agreement.

    Best Regards,
    Dimitar

    jQWidgets team
    http://www.jqwidgets.com/

    jqxgrid #69253

    apulcino
    Participant

    Hi Dimitar,

    I apologize for posting a portion of the source code — that was certainly an oversight on my part. I would gladly edit out the offending bits, but the forum apparently will not let me edit my previous posts. Is there a better location to submit bugs?

    Regarding IE8, I agree that the demos work fine. However, if you add an element with an id attribute set to “mid” on your page (e.g.: <div id=”mid”></div>”), you can reproduce the error. IE is reserving element id values in the global JavaScript namespace and your undeclared mid variable is finding that object reference.

    I have also verified that this bug happens in IE9 as well.

    Thanks,
    Andrew

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.