Help talk:Adding tooltips
Tooltips and div id
Here's something which may be worth adding to the documentation. Tooltips do not work in Semantic Forms when they are enclosed by div id-tags as used with the "show on select" function. Cavila 15:13, 22 November 2011 (CET)
- [View source↑]
|Thread title||Replies||Last modified|
|Adapting the layout of the tooltips||0||15:26, 7 June 2018|
|<info> tag equivalent to #info parser function?||1||12:52, 25 May 2018|
|How do we implement it ?||3||02:59, 11 July 2015|
|Tooltips with inline tags only are sad||2||23:53, 3 May 2015|
|Changing the skinning of the tooltip box?||0||12:16, 12 March 2014|
See this mainlinglist thread. Moreover the tooltip provides even more classes ready to be adapted.
AFAICS, the function of the
<info> tag is equivalent to the
#info parser function. If so, this should be mentioned in the documentation.
<info> tag at least allows using wiki syntax, compared to the parser function.
I tried to use this on my local installation and it does not work (show the icon but does not pop). I saw it in action on at least one other wiki and even here it does not consistently work. I like the idea and it's more elegant than footnotes in a form, but if is not documented on how to make it work properly. (sorry, I tought it did not work here, but it does not work in preview only).
It does work in preview as well  but if for some reason you have an extension that use JS differently as shown here  then JS execution is blocked which is a prerequisite for  being successful.
As in , find the malefactor, correct the JS, and you should be able to see that it works in  as well.
The reason for the mentioned "Error: Unknown dependency: jquery.delayedBind" as shown in  is mostly likely caused by the WikiEditor extension  (on this wiki).
I know nothing about JS so I do not want to mess into the files. I think that I will look into creating a template to do the same thing using some css.
There is still some job to do on my templates and forms, but I should soon have all what is needed to make a website to list japanese temples, then when I have enough entry, I can add shrine, castle, gardens.
After that, I will wait for a new release of semantic bundle and try to figure out if it's worth making a live website.
I don't think that adding a whole parser function that can only draw an icon and add
title attribute is worth it.
At least you could use jQuery tipsy plugin, that is bundled with MediaWiki and allows block HTML tags in the tips, as well as nested tips.
Whether this is sad or not I'm unable to argue with but it is a no-frills feature that was born out of the necessity to display information within SMW (jQuery tipsy was evaluated and did not support the features required).
The #info parser is an add-on (not really necessary for core but it was introduced some time ago) with a low barrier for technical adaption and is more or less maintenance free.
If a user wants to use somethings else it is entirely up to him/her to do so or if someone wants to submit a PR to improve the #info functionality that would be fine as well but no core developer will spend any time on improving #info because it does what it should do, provide a simple "info" about an entity marked by an icon to indicate the severity.
Well, it's up to SMW debelopers, but I did manage to use tipsy to display popups, with block HTML tags and nesting on my site.