07-22-2010, 07:53 PM
Well, I have little hope of a response given the level of activity here, but here goes...
I have this otherwise neat script installed in my web pages. However, it does two things that make it unacceptable.
1. If the page is within an iFrame (we have no choice at this point. We have to use an iFrame), the tooltips pop up outside of the frame and are therefore unreadable.
2. Sometimes the tooltips get stuck open and end up behind another tooltip, creating confusion for the visitor.
I can solve #1 by not allowing the tooltip to float around, but I can't solve 2. Is there a way to tune up this script so it's more responsive.
Please help. My only alternative to this is to go to Flash, and I hate Flash more than I hate iFrames.
07-22-2010, 11:17 PM
Well, you have to expect someone to ask... Why is it that you have to go with iframes?
Are the tooltips being generated from code in the iframe or the parent page? Are the parent page and the iframe on the same domain?
You can set a timer to close each tooltip. You would use setTimeout to create a timer for each tooltip when it is created. You would then need to create a function that checks to see if the tooltip 1) still exists, and 2) is no longer being hovered over -- if both are true, then kill the tooltip. Then set the timer to call that function on that tooltip in "x" seconds.
But we might not have to dig into the script if we can figure a better way to display your content in the first place. Iframes are almost never the answer.
11-13-2011, 05:33 PM
I have experienced the same problem, and I have determined it happens when the cursor moves off the hyperlinnk BEFORE the tootiip appears. It seems that in that case, the end of the mouseover event is lost, so the tooltip persists.
Just move the cursor quickly over either the sample hyperlink or the box below it -- or both.
I would like to know if there is any way to reduce the chances of this happening. It can happen rather often if the user's Internet connection is slowed, for any reason.
11-14-2011, 05:11 PM
I think this link roughly explains the basic idea of my earlier response to this thread:
You just use a named setTimeout (in other words, you assign it as a variable rather than simply starting the setTimeout - see below this post for a clarification) and a mouseover event on the tooltip to destroy that setTimeout if we ever get our mouse over the tooltip before the setTimeout actually fires (which we would not have done in the quick-pass situations you are seeing a problem with). You just need to make sure your setTimeout variable has global scope (in other words, declare it - even without any value - outside of any functions so that it is accessible to all other page functions).
Does that make sense?
//Simply calling a setTimeout:
//Setting a setTimeout call as a variable so we can access it later in order to cancel it:
var my_timeout = setTimeout('do_something',50);
//And then to actually cancel the named timeout you can do something like this:
You can brush up on setTimeout and clearTimeout use here, if it helps:
11-17-2011, 12:37 AM
I would like to have several different links each with an associated tooltip (and different tooltip files opened and displayed at run time), but so only one displays at a time.
Is there any text I can consult that would fill in the pieces that I'm missing?
I can open ajaxtooltip.js with Notepad++, but when I try that with jquery-1.2.2.pack, everything is on one extremely long line. Is there another editor that can display that file in a more usable form -- if it turns out I need to modify that file?