Fatih Solhan

Hi @micke-dahlgren, this issue should've been fixed with v-onboarding 2.8.1 Can you please make sure it's 2.8.1 and provide a reproduction of the issue with codesandbox?

thank you @iolk, I'll fix it

> Hi, @fatihsolhan > > thanks for your job; do you have any news about this problems? > > > > Thanks Hey @macJames976 sorry it's been quite busy weeks...

Hey everyone, The issue should be fixed now. It turned out to be a simple fix in the end. https://github.com/fatihsolhan/v-onboarding/commit/aa4e435fafc728bf99e298c3578ae6f907cde1a1 Initially, I thought adding `types` to the package.json would be...

Hi all! Thank you for the suggestion @rozsazoltan, I've checked the Popper library that we use for positioning but couldn't find this kind of feature. Can you let me know...

Hey @franck102 I appreciate your bug report and interest to v-onboarding. Could you please create a demo page on codesandbox or similar platforms to reproduce this issue better?

Hi @spencerjsmall Sorry for getting back to you so late on this one! I think I have a good solution for you - you can handle the moving elements by...

Hi @J-Michalek, Thank you for submitting this pull request. I will review both the PR and the related issue this weekend. If I need any additional information, I will reach...

Update: I noticed it's being used when it's in multiple mode:  https://github.com/primefaces/primevue/blob/312bf677ea06d92e84e9e4cb1c4001c755c6dd63/packages/primevue/src/autocomplete/AutoComplete.vue#L1-L4

@tugcekucukoglu Actually, @j0rgedev has already identified the root cause and proposed some solid solutions here. This seems like a legitimate bug where the AutoComplete component isn't properly using its own...