SelectMenu/Select: FieldGroup orientation leaks into trigger slot content
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Environment
- Operating System: macOS 26.6.2
- Node Version: v24.14.1
- Nuxt Version: 4.5.2
- Vue Version: 3.5.42
- Tailwind CSS: 4.3.3
- Package Manager: pnpm
Is this bug related to Nuxt or Vue?
Nuxt
Package
v4.x
Version
v4.11.1
Reproduction
Description
When a USelectMenu (same structure in USelect) is inside a UFieldGroup, components rendered in the trigger's #default slot inherit the field group context.
For example, a UBadge in the #default slot receives the fieldGroup: 'horizontal' variant classes:
not-only:first:rounded-e-none not-only:last:rounded-s-none not-last:not-first:rounded-none
Because the badge is the first child of the trigger button (followed by the label and trailing icon), not-only:first:rounded-e-none applies and the badge's right corners become square (computed radius: 4px 0 0 4px). The same select outside a UFieldGroup renders the badge correctly.
Created a PR
Additional context
No response
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction and compare USelectMenu and USelect inside and outside UFieldGroup. Trace how the trigger's #default slot receives field-group variant classes, then verify that a UBadge keeps its normal corner radius while the surrounding select still has the expected grouped styling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tailwindcss, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100