Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Tooltip position is broken by combination of position:fixed and transform:translate #3802

Closed
Nickproger opened this issue Jul 11, 2017 · 8 comments

Comments

@Nickproger
Copy link

Nickproger commented Jul 11, 2017

image

Do you want to request a feature or report a bug?
Bug.
The same issues as was closed before:
#2182
#3533
Why this PR wasn't marged?! It fix this problem!
https://github.com/tinymce/tinymce/pull/3030/files

What is the current behavior?
Move mouse over icons - tooltip has wrong position

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via fiddle.tinymce.com or similar.
https://jsfiddle.net/wkrzp4dc/

What is the expected behavior?
Tooltips should to have proper position.

Which versions of TinyMCE, and which browser / OS are affected by this issue? Did this work in previous versions of TinyMCE?
4.6.4

@DAbrashin
Copy link

@asadovnikov
Copy link

annoying bug

@vovashevchenko
Copy link

@valenburm
Copy link

the same

@rndmerle
Copy link

rndmerle commented Oct 5, 2018

Try to add position:static on body.

getPos util function from TinyMCE won't use getBoudingClientRect to get trigger element's position if the body isn't statically positionned (because left/top properties values applied on tooltip, which is a body child, wouldn't be accurate if body had margins for instance).

But using getBoudingClientRect is the only way to get the right element's coordinates when there is some parent on its own transformation layer.

@dotnetprofessional
Copy link

Ok, I think I know why this hasn't been fixed as its possibly an edge case scenario. If I run either Chrome or Edge browsers on my primary monitor (I have two), then it works as expected. However, if I use it on my secondary monitor it doesn't work and reproduces the original reported problem. So I'm not sure if that's a bug with the browsers or the product. I can repro this using the feature sample here:

https://www.tiny.cloud/docs/demo/full-featured/

@tiny-stale-bot
Copy link
Collaborator

This issue is stale because it has been open 365 days with no activity. Please comment if you wish to keep this issue open or it will be closed in 30 days.

@tiny-stale-bot
Copy link
Collaborator

This issue was closed because it has been stalled for 30 days with no activity.

@tiny-stale-bot tiny-stale-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants