Hi,
in my app my md-content has vertical scroll. When I hover over button to show tooltip and scroll has position 0, then tooltip appears in correct place. But when I scroll down, tooltip does not follow the scroll. Is appears over the button. Is it a bug or do I have something wrong with my layout? (I use flexbox...). Or maybe you could help me with telling how tooltip positions itself?
Thanks,
Pawe艂
I have the same behaviour too :(
It exists on current version of documentation:
These docs were generated from (v0.9.4 - SHA 2c41f0f) on (2015-05-15 05:44:27 -0700) GMT.
eg. https://material.angularjs.org/latest/#/layout/grid on Chrome 39, when accessing tooltips for "View Source"
+1. Is there any workaround possible? I use tooltips for a database scroll and the tooltips doesn't work at all currently in rc3. Thanks
I have looked into this briefly. I suspect #5654 might help here.
Same Problem here (rc3)... happens when scrolling inside md-content
+1
+1 (rc4)
@r0b- Can you check if #5809 works for you too? If so, you can close your PR please?
Looks good - Thanks!
When do you plan to merge it with the master?
So is this solved? I'm still getting that alignment problem and can't seem to find a workaround for it.
+1
This issue is closed as part of our 鈥楽urge Focus on Material 2' efforts.
For details, see our forum posting @ http://bit.ly/1UhZyWs.
Still happening on 1.0.9. Tooltip is showing, but the position is incorrect. It's out of the visible portion of the page, close to the top.
+1
Had same issue and modified the ns-tooltip's position from "absolute" to "fixed" and it looks fixed. Got the idea from the denied PR #5809 by @SanderElias , which actually uses this same logic but the use case seems narrow for my scenario so use with care.
Using version 1.1.0-rc2.
Kudo's to you, @lolptdr, for coming up with a solution for something that seems pretty trivial but still got the annoying 'blanket wontfix' answer.
Most helpful comment
Had same issue and modified the ns-tooltip's position from "absolute" to "fixed" and it looks fixed. Got the idea from the denied PR #5809 by @SanderElias , which actually uses this same logic but the use case seems narrow for my scenario so use with care.
Using version 1.1.0-rc2.