Translate3d on the parent (not necessarily direct parent) causes the tooltips to misalign and fire incorrectly in on Safari 8.0.6 (latest)

[mathew-kurian]

No description provided.

[Moussawi7]

@bluejamesbond ,
Same issue on Desktop browsers(FF,Chrome...).
Did you solve this issue?

[adamscybot]

This is a bug in the spec of transforms where a new coordinates system is created for every element that is transformed.

In theory, you could work around by calculating the position of the parent and passing the values to the offset prop.

[CremaFR]

@wwayne It seems when you refactored your code you removed the fix provided by the pull request. I upgraded from 3.0.0 to the latest and a simple translate3d(0,0,0) make the tooltip position bug again.

ps : you may try to use npm unpublish --force instead of increment your version number :-)

[wwayne]

@cremalex Good to know npm unpublish, it would be super useful for me, thank you. As for the translate3d fix, I was planning to improve that part, but I missed it, so please use old version for the moment, I will let you know when I fix this bug.

[wwayne]

@cremalex This has been released with 3.0.11

[CremaFR]

Thanks ! Just a question why not check if the current element is under a transform aswell?

In my case I have this :

<div className={ Button } style={ { transform : /* some react-motion transform */ } } data-for={id} data-tip>
    <i className='icon'/>
</div>

And I don't feel like adding an extra div just for my tooltip when we can check the current node element before checking the parent(s).

[wwayne]

Released 3.0.12, looks npm can't republish with same version

[CremaFR]

Oh well I checked the doc and yeah it looks like you can't.
With sinopia I can do it at work. My bad

[kpavankotesh]

I see this issue in IE11, any solutions?