MuiTouchRipple style overrides aren't applying
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start with the linked CodeSandbox reproduction in src/Demo.tsx and run it to confirm that the MuiTouchRipple theme overrides do not affect the button ripple. Trace the MuiTouchRipple styles and rendered button behavior, then verify that the documented override produces the expected ripple colors in the sandbox.
Written by the indexing model from the issue text.
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Current behavior 😯
With the following defined inside theme:
`{
components: {
MuiTouchRipple: {
styleOverrides: {
childLeaving: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
ripple: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
ripplePulsate: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
root: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
rippleVisible: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
child: {
backgroundColor: '#ff9900',
color: '#00ff00'
},
childPulsate: {
backgroundColor: '#ff9900',
color: '#00ff00'
}
}
}
}`
I'm not seeing the ripple colour on buttons change and I odn't see where the colors specifieid above apply to Muitouchripple on any level
Expected behavior 🤔
Colours defined in MuiTouchRipple override should apply to buttons.
Steps to reproduce 🕹
Steps:
- Use style override as provided
- Attempt to add a button and ckick it
or
View sandbox: https://codesandbox.io/s/material-ui-v5-theme-sandbox-forked-u228v?file=/src/Demo.tsx:0-1773
Context 🔦
No response
Your environment 🌎
`npx @mui/envinfo`
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
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.
More from mui/material-ui
-
type: new feature waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#48254 · 3 comments · 1 reaction ·
-
has workaround scope: avatar waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mui/material-ui#48190 · 5 comments ·
-
has workaround scope: typography type: new feature waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
mui/material-ui#46488 · 2 comments · 1 reaction ·
-
has workaround scope: text field type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#37216 · 6 comments ·
-
docs scope: autocomplete
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#35713 · 5 comments ·
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100