v1.3.2: Merge pull request #35 from jimdefrisco/init-fix

add some defense to catch console error

Polymer 1.x/2.x hybrid element support

v1.2.0

Design Refresh

• component redesign
• the tooltip-style property has been removed, use theming and css vars to style appropriately
• update documentation regarding mobile
• major bump to pick up redesigned sub-dependencies

v1.0.0-prerelease-4

update deps

v1.0.0-prerelease-1

component redesign

ensure tooltip stops showing and listening to events after being removed

v0.10.5

ensure tooltip stops showing and listening to events after being removed

Tooltip positioning and on-hover target can now be distinct!

Two large changes have been made to tooltip in v0.9.0.

First, no longer do the tooltip positioning and on-hover target have to be one and the same. This change was made so you can have a tooltip show up in another location (such as following your mouse while you hover over a chart). To disconnect positioning and hover, add the follow-mouse flag. You can then pass in any coordinates into mouse-coords as an x,y array, like [x,y]. You must do the mouse calculations yourself, but the tooltip will positing itself to whatever coordinates you input. Want it to be static but away from your on-hover target? Do the same and just pass in some static window coords.

The second big change is the ability to pass in an array of targets into the "for" property, be they IDs or elements. This way, you can have one tooltip activated by multiple DOM elements instead of needing a single tooltip for each DOM element.

Move to style modules and gulp

v0.8.2

Upgrade to Polymer 1.5.0

v0.7.0

Upgrade to Polymer 1.5.0

v0.4.0 changed internal tooltip behavior

• removed the position attribute, which wasn't needed anymore.
• changed the behavior of the component to ensure that the positioning will work every single time.
• updated internal comments and cleaned up code a bit.
• Added testing in line with our usual testing methods.