Hello, I want to add a little. I've been experiencing this issue since J 3.0 (J 2.5 and below was fine!), wrote on joomlacode org once, but they ignored the issue. For better view, install the plugin Tooltips from NoNumber, and try to "play" with tooltips over different objects (texts, images etc). It depends a little bit on the speed of going in and out of a tooltip. Since it's kind of very old bug, I want to see that it has at least medium priority and it's going to be fixed, is it? Thanks.

If it is an issue only seen when using an extension then perhaps the issue is with the extension?

No, no, that's for sure related to Joomla. The author of this topic wrote that it appeared in admin panel when hints ("help texts") are used.
The extenstion Tooltips from NoNumber is using these hints. I wrote about it to NoNumber, they answered that it's some kind of "a speed issue in jQuery/Bootstrap. Not much I can do about it." And with the extension it's just easier to see the issue...

For testing: tooltest.txt
It a table with tooltips, put it in a joomla article (NoNumber tooltips installed), try going in and out of ONE tooltip, fast, until it stops working at all. When it stops working (you don't see your tooltip or it blinks and dissappears instead of showing), you can mouse over another tooltip, this action fixes the problem. Hope explained well...

@creative3d based on the answer you received form NoNumber there is nothing joomla can do about it either as they are external libraries.

First of all, NoNumber could be wrong, they didn't do anything, secondly, it worked before 3.0, if it's a library problem, then it should be reported somewhere else. A lot of functionality on my site depends on these hints, and they don't work properly. And again one person had a quick look and decided to close the issue without solving it. That's not fare. Let someone look at it properly, let someone decide where the issue comes from and how to solve it, not just close it!

If NoNumber says the problem is not in the joomla core but in an external
library then I 100% trust his assessment

First of all, NoNumber could be wrong, they didn't do anything, secondly,
it worked before 3.0, if it's a library problem, then it should be reported
somewhere else. A lot of functionality on my site depends on these hints,
and they don't work properly. And again one person had a quick look and
decided to close the issue without solving it. That's not fare. Let someone
look at it properly, let someone decide where the issue comes from and how

to solve it, not just close it!

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/6981
https://issues.joomla.org/tracker/joomla-cms/6981.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#6981 (comment)

If the problem is in an external library, this library should be found and fixed somehow, don't you think so? I'm not a developer, so I can't do much here, especially when everybody says that's it is not their problem and closes topics. It's related to joomla, joomla uses it, joomla uses libraries with bugs, so we are all going to just ignore it, aren't we?
Have you reproduced the issue? Do you want me to create an issue here? What category?

If the issue exists in a third party library, then someone should report it to the library, but it isn't Joomla's job to filter issue reports and forward reports to third party teams. In the case of Bootstrap, they're probably going to ignore it unless it's a bug in 3.3 or the 4.0 dev branch so that leaves core hacking their library if it's a bug with Bootstrap 2.3. Either way, it's not a "well it's broken in Joomla so Joomla must find a way to fix it" scenario.

I'm not asking core hacking, it's just first of all, we don't know the cause of the issue yet, only assumptions, secondly, if joomla team can't do anything, then we need to report in the place that can do something. Right now if I stop writing, I see that everybody will forget about it immediately :) That's not good...