qtip("destroy") problem with jquery 1.3.2

[nevermore]

Hi, im experiencing a bug with qtip.

Im attaching dinamycally the qtip to a set of images when i click a div that acts like a menu.

The bug occours when i click another sub menu and i try to destroy the qtip with his target. The code is.

JS Code

$(".qtip-element").each(function() {
 
        if ($(this).data("qtip"))
        $(this).qtip("destroy").remove();
 
    });

I've already searched solutions and found this qtip version http://bazaar.launchpad.net/~craig.craig.../1.0/files witch fix it in Firefox 3.x but the bug remains in IE 8.

The debugger of IE8 shows the next error "unspecified error" in jquery-1.3.2.min.js, Line 19 Character 35440

witch is: var G=this[0].getBoundingClientRect();

Some help would be appreciate.

---

Almost forgot, the bug triggers when the page is scrolled and occours with jquery 1.4.2 too.

[Craig]

nevermore, could you provide the full stack trace for the bug your seeing please?

[nevermore]

Hi, the bug stack is.

1. api.updatePosition(event, true); line 59 jquery.qtip-1.0.js
2. position = target.offset(); line 1117 jquery.qtip-1.0.js
3. var box = elem.getBoundingClientRect() jquery-1.4.2.js

I have been debugging and found some interesting stuff. The cause of the bug is that qtip is trying to calculate the offset (2) to a target that no longer exist (watching the target variable found that has the same id of one of the images that i tried to destroy), in other words the images that i "destroy" previously.

"target" and "elem" in 2 and 3 seem to be the same variable and have some strange properties, like fileSize="-1", readyState="uninitialized" when the bug fires.

Dont know why this is happening since i'm removing the images with remove().

Maybe image cache of the browser is causing this?.

[Craig]

nevermore, it's possible this is caused by an related bug in the destroy method of RC3. Try upgrading the the latest branch release here: http://bazaar.launchpad.net/~craig.craig.../1.0/files