Replies: 3 comments 3 replies
-
This is, unfortunately, a limitation of the dropdown. It would resolve itself if it was hoisted to the body and we considered doing so when we were designing the input’s architecture, but doing so leads to a number of other issues that we decided would lead to a poorer DX than this shortcoming. We don’t have any immediate plans to fix this, but it’s worth keeping alive as a feature request under our discussions. |
Beta Was this translation helpful? Give feedback.
-
@justin-schroeder I'm looking into this issue in our project as well. We are using Quasar, which has its own portal setup for its components that have a popup of any sort, but I'm trying to stick with FormKit for inputs in this project for consistency & easier schema use. I understand the dilemma mentioned her & I found more detail in Discord. I have a question that MIGHT partially solve the issue around dropdown's. Have you investigated an input that uses the native input like the Another benefit to a component like this would be it would feel a bit more consistent if we wanted to mix the use of Even if this new component did not pick up the search capability, it would be nice for it to have the features for using a function to load options, etc. Perhaps that would be a good first step if this is feasible? |
Beta Was this translation helpful? Give feedback.
-
As of |
Beta Was this translation helpful? Give feedback.
-
Reproduction
https://formkit.link/caaebd1fa7385602b440ac3ad17d4102
Describe the bug
This is likely because the container for the list items is cut off. Might be fixed by hoisting it to the
<body>
Environment
• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]
Beta Was this translation helpful? Give feedback.
All reactions