ButtonProps className make SpeedDial unclickable
See original GitHub issue- This is not a v0.x issue.
- I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior 🤔
The button should get the class and still work.
Current Behavior 😯
It is unclickable (and in general all on<event>
methods won’t work).
Steps to Reproduce 🕹
Link: https://codesandbox.io/s/xon8qz939p
- Give speed dial
ButtonProps: {{ className: 'something' }}
Context 🔦
I was giving it a class to apply custom styles.
Your Environment 🌎
Tech | Version |
---|---|
Material-UI | v4.0.0-beta.1 |
React | 16.8.6 |
Browser | Chrome |
TypeScript | None |
etc. |
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
ButtonProps className make SpeedDial unclickable #15651
The button should get the class and still work. Current Behavior. It is unclickable (and in general all on<event> methods won't work).
Read more >How do I make <a> tags with a class unclickable?
I have some parent nav items with children and I don't need the parent items to be clickable. They look like this: <a...
Read more >material-ui/core/CHANGELOG.md - UNPKG
We will make the documentation of the v5 alpha releases available under ... 3462, - [SpeedDial] Fix classname override logic (#15652) @janhesters.
Read more >material-ui changelog
React components for faster and easier web development. Build your own design system, or start with Material Design.
Read more >front-end/node_modules/@material-ui/styles/CHANGELOG.md
A way to get location (latitude and longitude), elevation, speed and other relevant data from individual satellites from the Starlink constellation.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hburrows Thanks. I’ll mark the “future of SpeedDial” comments as off-topic to keep this issue on-point. We can open a new issue for this if it warrants further discussion on the future.
@oliviertassinari That is sad to hear. I think it would get more usage once it’s merged in core, but I’m biased 😄
Yep! I’m gonna do a quick PR.