-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Nuxt3] Combobox.Positioner incorrect position of content #2195
Comments
Here's the same example with Vue 3 and Vite, without SSR. You can see that the position of content is correct. |
Thank you for opening this issue. I think it's similar to the problem with |
@bogdan0083 I've also stumble upon this issue some weeks ago, it seems even though Nuxt has SSR support for Teleport sometimes it adds the There is, though, an implement coming up that maybe will fix this 🤔 |
Hmm, I've just tried your solution with But I guess |
Mostly Vue SSR behavior - we'd love to mimic the client-side Vue behavior but it'd lead to hydration errors. Nevertheless, with the linked PR it should work fine and follow the best practices 👍 |
@manniL @bogdan0083 @jeferson-sb This should be fixed in |
Description
Hey guys! Thank you for creating such a beautiful library ❤️
I created nuxt3 project and installed
@ark-ui/vue
library. Tried to use Combobox. It works, but position of content is calculated incorrectly. I expect it to be UNDER input field. Instead, it shows at the top left corner:Link to Reproduction (or Detailed Explanation)
https://stackblitz.com/edit/nuxt-starter-fzamjd?file=components%2FComboboxArk.vue
Steps to Reproduce
Nuxt 3
project (in my case it's3.10.1
version)@ark-ui/vue
Combobox
component (I use UnoCSS for styling, but no styles added forCombobox.Positioner
orCombobox.Content
:app.vue
:npm run dev
and see the result. Content has wrong position on open (it's in the top left corner. I expect it to be under input)Ark UI Version
@ark-ui/vue: 0.11.0
Framework
Browser
Firefox
Additional Information
No response
The text was updated successfully, but these errors were encountered: