You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#6503 - fix(Select/SelectMenu/InputMenu): add fallback for max-height [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Afaik I don't think this is a bug, as it's a limitations of virtualization as concept. As we cannot decide the widest of a an element that didn't even render yet
a workaround would be to add a fixed width, or trying to compute the width of he widest row by hand
Activity
coderabbitai commentedon Jul 24, 2026
🔗 Related PRs
#6503 - fix(Select/SelectMenu/InputMenu): add fallback for
max-height[merged]📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
al1maher commentedon Jul 27, 2026
Afaik I don't think this is a bug, as it's a limitations of virtualization as concept. As we cannot decide the widest of a an element that didn't even render yet
a workaround would be to add a fixed width, or trying to compute the width of he widest row by hand