…e.g. for table cells), incl. test

…isibility: hidden closes the calendar - target is the root node instead of the button.

If the next/prev month buttons are hidden via visibility: hidden and the user clicks on the area where the button is after it's been hidden, the click event's target ends up being the root node. The code that checks for this expects the event to be a child of the root node instead of the root node itself, so this patch just adds a check for this.

rather than checking if any tooltips already exist.
this way tooltips on some elements that are reloaded via
ajax calls will continue working. the previous code would
assume all tooltips still exist if *any* of the tooltips still
exist -- even if some of them no longer exist. now, part of a
page may be changed and can have new tooltips created instead
of only the ones for elements that did not change.

resolves: #349

Signed-off-by: Adam Mckaig <adam.mckaig@gmail.com>

Conflicts:
	README.md

… right after. Enables chaining using the onClose callback method

Fix for issue #480

Fix for issue #563

fix unexpected behavior when calling $('my_selector').tooltip() a second time on altered elements

Fix for clicking on the next/prev month button hides calendar

Added support for enclosing tooltip inside trigger element (2nd try)

Patch 3

…ry 1.8

When using jQuery 1.8+ with some older components (e.g. jQueryUI), outerHeight() and outerWidth() get "duck punched" and they return an object instead of the expected numeric value.  Passing false (which is the default value) fixes the problem.