Hi @seekbeacon
Can you explain further or give an example ?
I have a term Gb/Eo where the ‘b’ and ‘o’ are subscripts, but are not recognised from Gb/Eo in Tooltipy entry. Case sensitivity is not set.
Hi
I think the problem here is with the forward slash character “/”
plz try to use another character instead and see
Thanks, but the slash is essential as it’s a technical definition, and removing the slash would make it meaningless. Is there not a fix too come in the future?
Not even if we pay for it?
H @seekbeacon
It’s not a problem of paying it’s just a problem of time
I will check when available and update you here
thanks
OK, thank you, appreciate it. The issue by the way is not related to the forward slash, as there are other terms with a slash (e.g. G/T) but no subscript which are fine.
After a little more troubleshooting, the issue appears to be caused by having the html <sub> tag (for subscript) inside the target string. If there is a way of tweaking the code so that it ignores any html tags inside the search string, that would fix it.
You mean I should escape the tooltips from HTML tags ?
Well yes, why not? They shouldn’t form part of the search string, to my mind anyway.
