Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[MaterialButton] Change button insets programmatically especially since they don't default to 0dp
See original GitHub issueIs your feature request related to a problem? Please describe. This might be more of question than a request, but I’m not sure why we would want inset at the top and bottom by default. I understand that the property could be of use, but I end up removing the inset by default in all my apps through a style like so:
<item name="android:insetTop">0dp</item>
<item name="android:insetBottom">0dp</item>
- Could you provide more info for having inset having a value greater than
0dpby default? - Is the inset related to elevation and shadow?
Describe the solution you’d like
Set the default inset of buttons to 0dp.
Describe alternatives you’ve considered
As an alternative, and if the inset is related to the shadow from the elevation, maybe the UNELEVATED style could reset the inset to 0dp?.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Has there been any progress on this?
The insets exist as part of ensuring the touch targets are large enough for mobility impaired users with the default style, so we’re unlikely to change them. We recommend at least 48dp as a minimum touch target.
That said, it seems completely reasonable to want to change them programmaticly, so I’ll update the issue to reflect that.