-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[Button] Fix disableRipple getting ignored in MuiButtonBase defaultProps #29613
Closed
ZeeshanTamboli
wants to merge
3
commits into
mui:master
from
ZeeshanTamboli:issue-29598-Theme-disableRipple
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may look dubious. But if I instead do
disableRippleProp || disableRippleContext
, the individual buttons havingdisableRipple={false}
do not take priority over theme'sdefaultProps.disableRipple
.false || undefined
equalsundefined
anddefaultProps.disableRipple
still wins (Reason to add the second test case).And if we do
disableRippleProp ?? disableRippleContext
, theButtonGroup
behaviour will change as discussed in #28645 (comment) and would be a breaking change.This change ensures both
ButtonGroup
and theme'sdefaultProps.disableRipple
works as expected like before v5.1.0 along with keeping the use ofReact.Context
API.I know this is confusing, another better solution without any breaking changes would be appreciated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't
disableFocusRipple
,disableElevation
,disabled
,fullWidth
, etc. suffering from the same kind of priority issues? I don't feel like we took my comment in #28645 (comment) into account.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all of them has issues.
disableRipple
is the only regression from v5.0.6 to 5.1.0.disabled
does not work since long with theme's defaultProps ofMuiButtonBase
applied toButton
.Others work since they are of
MuiButton
slot.We did not consider it as more bugs but a change in behaviour resulting in it being a breaking change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ZeeshanTamboli can we add tests for all of these props and make sure they work the same?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An example that demonstrates that 1. the proposed fix is not working 2. the other props are impacted https://codesandbox.io/s/basicbuttongroup-material-demo-forked-65rk8?file=/demo.js. Button 2 should have a ripple and Button 3 should not be full width.