[Bug Report][3.4.6] Disabling utility classes breaks some components blueprints and styling
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41k
- Forks
- 7.1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 11
Description
Environment
Vuetify Version: 3.4.6
Vue Version: 3.3.11
Browsers: Chrome 120.0.0.0
OS: Mac OS 10.15.7
Steps to reproduce
- Clone https://github.com/mcfarljw/vuetify-disabled-class-utilities
- Run
npm i - Run
npm run dev
Expected Behavior
Disabling utility classes doesn't break the default Vuetify components.
VBtnshould be rounded with a cursor on hoverVTabshould use the correct colors with a cursor when hovering and be roundedVNavigationDrawershould not have a border
Actual Behavior
Disabling utility classes cases several components to not be styled correctly.
VBtnis not rounded without a cursor on hoverVTabis not the correct color when hovering and is not roundedVNavigationDrawerhas a border despite it being set to 0
Reproduction Link
https://github.com/mcfarljw/vuetify-disabled-class-utilities
Other comments
In general I've been having a lot of trouble following the documentation for SASS Variables (https://vuetifyjs.com/en/features/sass-variables). I'm trying to disable the utility classes so that I can use TailwindCSS, UnoCSS, or PandaCSS without conflicts but in this example I'm just trying to disable the utility classes without breaking the default styling based on the selected blueprint.
Utility classes disabled:
Utility classes enabled:
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 by running the linked reproduction repository with npm i and npm run dev, then inspect how disabling utility classes interacts with the documented SASS Variables configuration. Compare VBtn, VTab, and VNavigationDrawer against the listed expected behavior; done means those components retain their blueprint styling when utility classes are disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sass, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100