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
MudSwitch: When disabled, the ripple effect still shows #4339
Labels
triage
Investigation required
Comments
snehabihani
added a commit
to snehabihani/MudBlazor
that referenced
this issue
Apr 4, 2022
Garderoben
pushed a commit
that referenced
this issue
Apr 4, 2022
@snehabihani Thanks! |
jammerware
pushed a commit
to jammerware/MudBlazor
that referenced
this issue
Sep 20, 2022
jammerware
pushed a commit
to jammerware/MudBlazor
that referenced
this issue
Sep 20, 2022
jammerware
pushed a commit
to jammerware/MudBlazor
that referenced
this issue
Sep 20, 2022
jammerware
pushed a commit
to jammerware/MudBlazor
that referenced
this issue
Sep 20, 2022
3dots
pushed a commit
to 3dots/MudBlazor
that referenced
this issue
Mar 23, 2023
ferraridavide
pushed a commit
to ferraridavide/MudBlazor
that referenced
this issue
May 30, 2023
ilovepilav
pushed a commit
to ilovepilav/MudBlazor
that referenced
this issue
Nov 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug type
Component
Component name
MudSwitch
What happened?
Clicking on a disabled MudSwitch still shows the ripple effect, while it should not.
Workaround for now: Bind both the
Disabled
andDisableRipple
properties to the same bool var.Expected behavior
When the
Disabled
property is set totrue
, the ripple effect should not show.Reproduction link
https://mudblazor.com/components/switch#switch-with-label
Reproduction steps
Relevant log output
No response
Version (bug)
6.0.9
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request
Code of Conduct
The text was updated successfully, but these errors were encountered: