This merges multiple patches from forks on github.

Specifically: Style (trailing spaces) has been fixed by multiple parties on() vs live() in newer versions of jquery Fixes to SVG behaviour (use of getBBox()) Ability to inject a custom css class ... and more.

This lets you select/copy text, interact with HTML content, etc.

It's also needed if you tweak the position of the tooltip (via CSS) to have it overlay the target element instead of go around it; in this case, the former behavior caused the tooltip to flicker if you moused over it.

It happens to me that when I add a tipsy tootip to a big text input field there is a black arrow. A picture is worth a thousand words: http://img406.imageshack.us/img406/4645/bugtipsy.png

I hope it helps, and you can fix it. Thanks

This allows something like:

$('#example').tipsy({
    title: function() {
        var tip = $('<span>Loading...</span>');

        $.getJSON('http://example.com/data.json', function(data) {
            tip.text(data.title);
        });

        return tip;
    }
});

This allows for temporarily disabling tipsy tooltips. This is useful when you have animations or other situations where tooltips are problematic or cause extra noise.

$.fn.tipsy.disable(); // Disable tooltips
$.fn.tipsy.enable();  // Kitten attack! j/k, this turns tooltips back on again.

Tipsy in first line of README.md has misleading statement

Released under The MIT License.

Effectifly it is not. At the bottom of the same README.md file there is a statement which put additional restriction:

By forking this project you hereby grant permission for any commits to your fork to be merged back into this repository and, with attribution, be released under the terms of the MIT License.

So, anyone who is "forking" tipsy MUST grant permission to release code back under the terms of MIT license. This restriction has ideas similar to GNU GPL licence and put sensitive limits on library usage and adoptation.

Is it unacceptable to some environments to use code with such restrictions.

Another issue is that statement is questionable from the legal standpoint. For example the meaning of term "forking" is not well defined.

If the original intension was to cleary define licence of code pushed back by contributors i sugest you to define developer policy as in, for example LLVM project:

As a contributor to the project, you agree that any contributions be licensed under the terms of the corresponding subproject. (source)

Another option is to use Apache 2.0 license. From wikipedia:

The Apache License is permissive, so it does not require modified versions of the software to be distributed using the same license (unlike copyleft licenses - see comparison).

Unless explicitly stated otherwise, any contributions submitted by a licensee to a licensor will be under the terms of the license without any terms and conditions

Like any free software license, the Apache License allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software, under the terms of the license.

Hope you clarify on that issue. Thank you.

Is it possible to set tooltip 'width' with js codes? I don't want to set tooltip width with css. I am using your tooltip for text and images. Sometimes i got big images. So pictures overflows tooltip. If i can set tooltip width with js i can select custom width's for custom class or id's. Thank you, for your great work... For example:

$('.text').tipsy({width: 200}); $('#image-1').tipsy({width: auto'});

Hi there,

in my use case i need to unbind the jQuery.tipsy() plugin or the hover effect who was setted up by tipsy(). The problem is the configuration in tipsy().

Please implement a simple unbind method:

jQuery('selector').tipsyUnbind();

Greets, Marc

If you have a jQuery object and you call

$obj.tipsy('hide');

when $obj hasn't been tipsy-fied yet, you get

Uncaught TypeError: Cannot read property 'hide' of null

You might ask "well, why would you do that?" The answer is that I'm using live: true to make $obj tipsy on an as-needed basis; if you make the $obj.tipsy('hide'); call after someone's hovered over it, you don't get an error.

I've taken to using

if ($obj.data('tipsy')) { $obj.tipsy('hide'); }

as a workaround, but this is obviously a hack.

i.e. 8 compass points instead of 4

I've been thinking about this for ages now, pretty much since I released the project. If enough people vote this up I'll look at adding it in.

-J

Currently tipsy shows an empty tip if the title is empty (like title=""). IMO it should only be active if there is a title != " " or ""

When the custom className has styles which alter the height and width of the tipsy, adding the className after setting position causes the tipsy to be off positioned with respect to its element.

I've been using this library with D3, and noticed that the tooltips position themselves in the upper left corner of the screen when using Chrome.

this.$element.offset() was returning { top: 0, left: 0 }. I'm guessing this has to do with Webkit browsers and the way my D3 plots are rendered.

This branch replaces the call to $.extend({}, this.$element.offset(), {}) with this.$element[0].getBoundingClientRect(). This adds a few extra attributes to the pos object, but solves the issue and should work the same.

Can we have four tipsy titles on one element? Something like:

<span title="Normal Title" data-tipsy-ctrl-title="With Ctrl Key" data-tipsy-alt-title="With Alt Key" data-tipsy-shift-title="With Shift Key">Some sentence</span>

Just an idea, but what if more than one keys are pressed at the same time?