Replacement for on: 'auto' in version 11?
#2259
Replies: 2 comments 1 reply
-
|
@KeithGillette thanks for reaching out. Could you please describe the behavior that |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @RobbieTheWagner. I'm not sure if it's due to a subsequent Floating UI release but in testing again, positioning seems much improved. In my previous testing, the update seemed unusable. Now, the positioning is not as elegant but passable. The arrows still aren't centering in the elements as the were before (shown in the comparison screenshots below) but at least the target is unambiguous and unobscured. Popper Floating UI Popper Floating UI |
Beta Was this translation helpful? Give feedback.
-
|
@KeithGillette hmm, it should be better centered than this. Would you be able to create a small reproduction in stackblitz or something similar? |
Beta Was this translation helpful? Give feedback.
-
We've been using Shepherd through the
angular-shepherdwrapper. Upon upgrade toangular-shepherd@15.0.0, which updates toshepherd@11.0.1, we found that the previouson: 'auto'PopperPlacementsetting supported by Popper.js has been removed. We foundautopositioning worked extremely well but the Floating UI placement options result in placements that put the arrow in the wrong place or obscure the element being pointed to with the Shepherd tour overlay. Isautocoming back?Beta Was this translation helpful? Give feedback.
All reactions