vuetifyjs/vuetify

[Bug Report][3.8.6] Incorrect label positioning when using outlined variant and rounded

Open

#21,486 opened on May 26, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (7,139 forks)batch import
C: VFieldE: roundedT: bughelp wanted

Repository metrics

Stars
 (40,995 stars)
PR merge metrics
 (Avg merge 36d 4h) (23 merged PRs in 30d)

Description

Environment

Vuetify Version: 3.8.6 Vue Version: 3.5.15 Browsers: Chrome 136.0.0.0 OS: Mac OS 10.15.7

Steps to reproduce

  1. Use a Vuetify input component (e.g., v-text-field).
  2. Set the variant prop to "outlined".
  3. Set the rounded to prop like "lg" or "sm" not the full rounded one.
  4. Add a label prop.
  5. Focus the input or enter text to trigger the floating label.

Expected Behavior

The floating label should align vertically with the input text and the outlined border.

Actual Behavior

The .v-field__outline__start class contains a flex-basis property, which causes misalignment with the input text.

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

If this behavior is intentional, there should be an option to align the label correctly.

Contributor guide

Research direction
Look at the Vuetify source code for the outlined variant label positioning. The issue identifies the .v field outline start class with a flex basis property causing misalignment. Check the reproduction link and examine the CSS in files like packages/vuetify/src/components/VField/VField.sass or similar. Consider if adjusting flex basis or using alignment properties can fix the label position without breaking other variants.
Tech stack
typescriptvuecss
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
basic CSSunderstanding of flexbox
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70