Replacement for on: 'auto' in version 11?
#2259
Unanswered
KeithGillette
asked this question in
Q&A
Replies: 2 comments 1 reply
|
@KeithGillette thanks for reaching out. Could you please describe the behavior that |
0 replies
|
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. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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?All reactions