Closed (won't fix)
Project:
Footnotes
Version:
5.x-1.0
Component:
Footnotes
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Mar 2007 at 12:51 UTC
Updated:
29 Mar 2010 at 05:51 UTC
Jump to comment: Most recent
Comments
Comment #1
beginner commentedyou mean this:
http://p4.sme-ccppd.org/beta.soundandmusiccomputing.org/node/598
(hover over the [1])
It's nice, but it works only with javascript on. The current tooltip solution is low key and works everywhere. A more elaborate solution could be adopted, but it would need to degrade well to that the tooltip like the current one would still work when there is no javascript. And the two solutions must 'cooperate' (i.e. not have the two tooltips appear at the same time).
Comment #2
hingo commentedOf course. I didn't look at the hover tips module yet, but that is something that of course we would expect from it.
(But good that you brought it up, in case someone reads this and starts doing something.)
Comment #3
hingo commentedI've now had a look at the hovertip module at http://drupal.org/project/hovertip
On a quick glance, it seems it depends on sending invalid html to the browser. The functionality is based on JavaScript that uses custom html element attributes:
This is an example of a <span hovertip=htdef>hovertip</span>(seen in a page that uses hovertip)As such, I will not integrate this into Footnotes. (It should be noted, that there definitively is a way to implement the exact same hovertip functionality without relying on invalid html. Not to mention that the author even seems to be sloppy with remembering the quotes around attribute values in his own examples...)
Comment #4
wayland76 commentedJust so I understand, would this be class="hovertip-htdef" or something?
Comment #5
hingo commentedHi Wayland
The example link from hovertip project page http://drupal.org/project/hovertip leads to http://www.dave-cohen.com/node/1186
From there:
There are several problems with incorrect html here
When I had a brief look it seemed like the javascript code in hovertip depends on these erroneous uses of html, so one would have to make some changes to the code to get away from these problems. But it is certainly possible to do the same thing the right way, in case you are interested to try.
Comment #6
wayland76 commentedI can see the answers to problems 2 and 3, but I'm afraid I don't see how to do problem 1 the right way :).
Comment #7
hingo commentedWayland,
for #1, consider using
<span class="hovertip">and then searching for that from javascript. You should be able to get all the same results as now, but with valid html.Then to get the italics (or whatever formatting you want), use css:
Btw, are you the author of Hovertip?
Comment #8
wayland76 commentedNo, I'm not, but hopefully I can help get the right information to the right places :).
Comment #9
Anonymous (not verified) commentedIt appears that the hovertips module *can* be made to produce valid HTML (instead of that awful junk). See the comment titled "Can be valid" on http://www.dave-cohen.com/node/1186 . Why it does not do this by default I did not understand clearly.
If I do an integration that works and produces valid HTML, and provide a patch, would it get committed into the dev version? (Subject to code review and so forth.)
Comment #10
hingo commentedI'm open to including it, yes.