-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[ButtonBase] Fix missing keyboard ripple #8723
Conversation
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.
I'm not sure it's going to be enough. I can't see the pulsating mode of the ripple navigating to the Button documentation page. I'm wondering what's missing 🤔.
src/ButtonBase/ButtonBase.js
Outdated
@@ -41,6 +41,10 @@ type ProvidedProps = { | |||
|
|||
export type Props = { | |||
/** | |||
* If `true`, the ripple will me active on mount |
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.
Missing dot at the end.
@oliviertassinari ah i added start() instead of pulsate() - should pulsate now :) but i have to investigate how this is working internally - i think there is still sth wrong with keyboard focus |
Nop, that won't make it, the pulsation state needs to be in sync with the focus state. I'm looking into it. |
event.persist(); | ||
const keyboardFocusCallback = this.onKeyboardFocusHandler.bind(this, event); | ||
detectKeyboardFocus(this, this.button, keyboardFocusCallback); | ||
// Fix for https://github.com/facebook/react/issues/7769 |
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.
It doesn´t working yet.. even in the demos. https://material-ui.com/demos/dialogs/ |
Hopefully this is the fix for #8438Olivier edits:
I have changed my mind. I don't think that the pulsation display should be the default behavior for the
autoFocus
property. It feels too opinionated. For instance, it's not how a native input behaves.I would rather see people opting-in this behavior with #3008.
Still, I have found a bug with the keyboard display of the ripple. We are good now:
Closes #8438