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
Placements other than top, bottom, left and right are not working as intended for the popover and tooltip components.
For instance, if you specify top-left, then the placement will be the same as top.
Note, I've also tried other directional properties such top-start in favor of top-left, which also resulted in the same outcome as above.
Any update on this? Did some investigation happen? I've encountered this exact issue after updating from v11 to v14 during a big dependency update to get a project up to date again and now I get complaints that the tooltips look wrong.
Bootstrap doesn't have `top-left`, `top-start` composite placements and it leaves the padding that interferes. This commit removes the padding.
Fixesng-bootstrap#4369
Bootstrap doesn't have `top-left`, `top-start` composite placements and it leaves the padding that interferes. This commit removes the padding.
Fixesng-bootstrap#4369
Bootstrap doesn't have `top-left`, `top-start` composite placements and it leaves the padding that interferes. This commit removes the padding.
Fixes#4369
Bug description:
Placements other than
top
,bottom
,left
andright
are not working as intended for the popover and tooltip components.For instance, if you specify
top-left
, then the placement will be the same astop
.Note, I've also tried other directional properties such
top-start
in favor oftop-left
, which also resulted in the same outcome as above.It was last working in v11:
https://stackblitz.com/edit/angular-h4rwfs?file=src%2Fapp%2Ftooltip-basic.html
Link to minimally-working StackBlitz that reproduces the issue:
https://stackblitz.com/edit/angular-d7cxo4?file=src%2Fmain.ts,src%2Fapp%2Ftooltip-basic.html
Versions of Angular, ng-bootstrap and Bootstrap:
Angular: 14.1.0
ng-bootstrap: 13.0.0
Bootstrap: 5.20
Popper: 2.10.2
The text was updated successfully, but these errors were encountered: