You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Part of Popover is outside boundaries of viewport #19279
Edit: I just checked out the PR. It fixes the problem of the tooltip/popover being outside of the viewport but the arrow is not in the correct location.
Can be fixed with constraints: [{to: 'window', attachment: 'together', pin: true}], but the arrow is in wrong position. Please, do something with popover, this widget is really important but so broken in v4.
Activity
hebbet commentedon Feb 20, 2016
looks like your browser zoom is not at 100%.
martinfojtik commentedon Feb 20, 2016
yes, it's true, but problem occurs even if zoom is 100%
[-]Popover is outside of browser visible area[/-][+]Part of Popover is outside boundaries of viewport[/+]kybishop commentedon Feb 21, 2016
This also occurs with tooltips. I'd wager the problem is related.
jipexu commentedon Mar 6, 2016
Hi
Sorry but i have also this tooltip problem? is it fixed or not or is there a way to avoid this ?
Thanks
omnibrain commentedon Dec 22, 2016
Any chance this fix will be in alpha 6?
Edit: I just checked out the PR. It fixes the problem of the tooltip/popover being outside of the viewport but the arrow is not in the correct location.
Joyrex commentedon Jan 11, 2017
Still an issue in α6 - did this get introduced with the switch to Tether? v3 did not have this issue...
jipexu commentedon Jan 11, 2017
yes same behavior even in alpha doc ...
Joyrex commentedon Jan 11, 2017
Wasn't the auto value v3 had (that is dropped in v4) is what prevented tooltips and popovers from leaving the viewport?
alecpl commentedon Mar 10, 2017
Can be fixed with
constraints: [{to: 'window', attachment: 'together', pin: true}], but the arrow is in wrong position. Please, do something with popover, this widget is really important but so broken in v4.mscudlik commentedon Apr 25, 2017
same issue here, please fix :)
Johann-S commentedon May 14, 2017
Closed by #22444