Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I'm not able to change vs--disabled background styles #1831

Open
FabianGML opened this issue Apr 23, 2024 · 3 comments
Open

I'm not able to change vs--disabled background styles #1831

FabianGML opened this issue Apr 23, 2024 · 3 comments
Labels

Comments

@FabianGML
Copy link

Please respect maintainers time by filling in these sections. Your issue will likely be closed without this information.

  • Vue Version: 3.4.19
  • Vue Select Version: 4.0.0-beta.6

Describe the bug
When I add a disabled attribute to the v-select component, adds a new class named: 'vs--disabled'.
I've been able to change the border and other styles, but i have a problem with the background, I saw in the docs that i can override the global variable --vs-state-disabled-bg, but this doesn't work as well

Steps To Reproduce
Just add a disable attribute and try to change the background color

Expected behavior
Handle the background color as my system needs

Screenshots
Captura de pantalla 2024-04-23 a la(s) 3 47 27 p m

@FabianGML FabianGML added the bug label Apr 23, 2024
@hbiblia
Copy link

hbiblia commented Jun 24, 2024

.vs--disabled .vs__dropdown-toggle,
.vs--disabled .vs__clear,
.vs--disabled .vs__search,
.vs--disabled .vs__selected,
.vs--disabled .vs__open-indicator {
    background: red;
}

@FabianGML
Copy link
Author

I've already tried that, i've tried to change --vs-state-disabled-bg and --vs-disabled-bg css var as well and I just not been able to change the color, somehow the default css vars overlaps my own css

@FabianGML
Copy link
Author

the way that i manage to change the bg color, is to put !important to the end of the line
--vs-state-disabled-bg: #2A323C !important;
however, i don't think this is a good practice, but it was the only way i could change it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants