fix(InputMenu/Select/SelectMenu): add min-w-fit to content slot

[hanneskuettner]

🔗 Linked issue

#3920

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Let's try this again. As #3922 (comment) points out the previous PR fell victim to the large merges that happened in the neutral utility PR.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[benjamincanac]

Damn, sorry about that. I might have messed up somewhere 😬

[hanneskuettner]

Damn, sorry about that. I might have messed up somewhere 😬

No worries! That truly was a mean PR to keep updated with main 😅

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@4010

commit: 6b0d529

[benjamincanac]

Are you sure this is really a good idea? 🤔 Should not happen for this case:

https://ui.nuxt.com/components/select-menu#with-filter-fields

[hanneskuettner]

Are you sure this is really a good idea? 🤔 Should not happen for this case:

Hmm I agree that this is not really desired for the case you are showing... On the other hand, I seems super desired for that the trigger does not have an explicit width set, like in the original issue. 🤔

I'm also happy if we revert this, because arguably your example is a lot worse than the original issue, IMO and the user can deal with this on a case by case basis.

Or we can make it a prop on the component if it is something we want to support natively. Not sure what the best way is and I will defer to you entirely there.

[benjamincanac]

I've reverted it, it's easy enough to do :ui="{ content: 'min-w-fit' }" I guess.