Hi all, Using ASP.NET 3.5
I recently upgraded my ClueTip js file. I created a few new cluetip instances around my site, and all seemed well, however, when I went to test one of the first pages I ever wrote (which used a cluetip from V0.9.8), I found that it had broken. This is the normal behaviour: I have dropdown list, with a small img next to it. On first load, the Title attribute of the img is set from the DB, as is the Rel Attribute. The Rel attribute is pointing towards an HTTP Handler at the server, where it finds some text and an image from the DB. It has a class of 'tip'. Cluetip is bound on document.ready. If I change the drop down list an ajax call will go back to the server, work out some pricing, and come back to my js script, whereupon it changes the html markup of the image attributes 'rel' and 'title'. The same script re-binds cluetip by calling a seprate function that simply binds all elements with a class of 'tip' to cluetip. Following this, the user can hover over the image and hey presto the cluetip is relevant to the drop list content. Now then, after updating to the new version of cluetip, I do not get this behaviour. Instead, when I canhge the dropdown list, the code makes its ajax call to the server, comes back with the price, changes the rel/title attributes and re-binds cluetip; but it seems this rebinding is breaking the code, and so the scripts stop working altogether. If I swap the js file for the old one, it works perfectly (although another part of the site that I wrote using the new js file doesn;t work with the old version!) I haven't a clue as to what's gone wrong, but I suspect it's to do with the rebind. I have checked the setting parameters to make sure that I am not calling anything old with the new code etc. I have checked my ajax calls, they are fine. It's definately a cluetip problem, caused by this upgrade.... but what could be so different?
