Michał Dudak
Michał Dudak
There seems to be a problem with the publication date still. Do you intend to fix it in this PR or is it solely about the preview image?
Yeah, that's strange indeed. Let's merge what we have. It's an improvement anyway.
@oliviertassinari could you shed some light on why this was implemented this way? I haven't found any mentions of circular focus indicators in Material Design docs.
Let's just fix it. @mlgrn would you like to take a shot at it?
:+1: Agreed. @alisasanib could you take Olivier's comment into consideration in your PR?
I believe @oliviertassinari meant to remove the ripple completely when focusing and leave just the changed background color, as shown on the demo: https://material.io/components/buttons#interactive-demo
> There is also a change in the shadow when focused We do move the shadow when focused: **Material UI:** https://user-images.githubusercontent.com/4696105/199466639-652599f9-f80e-4338-969e-558a1bce72a4.mov **Material Design 2:** https://user-images.githubusercontent.com/4696105/199466656-8686139d-206d-4906-8e02-25f7a1fbfa53.mov As for the breaking change...
@oliviertassinari > taking a path that doesn't minimize breaking changes to reach the consistent state Could you explain what you mean by that? We don't introduce breaking changes in stable...
I've changed the approach based on the results of the [poll](https://github.com/mui/material-ui/discussions/34069). Snapshot:  All components, regardless of the package they belong to, will use the `.MuiComponentName-slotName` pattern. So `.MuiButton-root`, `.MuiSwitch-track`,...
Yes, I think .Mui-JoyUI makes sense (cc @siriwatknp). > It makes me think that if we wanted to optimize for the developers that write raw CSS (same hand muscles used...