Last modified: 2014-07-03 22:26:12 UTC
Current behaviour: * If you create a tooltip using tipsy, the tipsy-tooltip-container is appended to document.body Evidence: $tip.remove().css({top: 0, left: 0, visibility: 'hidden', display: 'block'}).appendTo(document.body); * This leads to a problem with scrollable elements (other than HTLM/body): ** When you scoll that element, tipsy remains where it is, while the element moves away. Consequently tipsy points to a wrong element ** When you scoll the body, but have a position:fixed element, tipsy scrolls away while the element remains where it is. Expected behaviour: * Tipsy always points to the right element, despite scrolling etc. Possible solution: * Allow specifying the element, the tipsy-tooltip-container is appended to or do intelligent guessing on it (which will be really challenging, I guess)
Also a problem with fullscreen; the tooltip container is appended to the body, and in fullscreen mode the element on which requestFullscreen() was called basically acts like the body and everything outside it is not rendered, so the tooltips just disappear. (changing severity since the current fullscreen and scroll behavior is clearly wrong)
There is a pull request for the position:fixed issue: https://github.com/jaz303/tipsy/pull/146