vuetifyjs / vuetifyjs/vuetify

[Bug Report][3.4.6] Disabling utility classes breaks some components blueprints and styling

Open
#18,846 9 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

sass T: bug
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
  1. Clone https://github.com/mcfarljw/vuetify-disabled-class-utilities
  2. Run npm i
  3. Run npm run dev
Expected Behavior

Disabling utility classes doesn't break the default Vuetify components.

  • VBtn should be rounded with a cursor on hover
  • VTab should use the correct colors with a cursor when hovering and be rounded
  • VNavigationDrawer should not have a border
Actual Behavior

Disabling utility classes cases several components to not be styled correctly.

  • VBtn is not rounded without a cursor on hover
  • VTab is not the correct color when hovering and is not rounded
  • VNavigationDrawer has 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:

CleanShot 2023-12-29 at 15 41 45@2x

Utility classes enabled:

CleanShot 2023-12-29 at 15 41 19@2x

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.