There are still some iOS 13.4 betas floating around that had not yet introduced this API. This
change should prevent those users from crashing when attempting to get/set this value.
PiperOrigin-RevId: 326248791
This commit adds the ripple maximum radius API to match the inkMaxRippleRadius API that are soon to be deprecated. This also moves those APIs to a "ToBeDeprecated" category. In this commit I set an ivar instead of having pass through properties because in a follow up I think it would be a good optimization to have the ripple be lazy until a user interacts with the button. This will lower initialization time and make the setters potentially faster. Since we don't have pass through properties I defaulted it to 0 to match the legacy API from `MDCStatefulRippleView` to match here.
PiperOrigin-RevId: 323011293
This commit adds the ripple color and ripple style APIs to match the inkColor and inkStyle APIs that are soon to be deprecated. This also moves those APIs to a "ToBeDeprecated" category. In this commit I set an ivar instead of having pass through properties because in a follow up I think it would be a good optimization to have the ripple be lazy until a user interacts with the button. This will lower initialization time and make the setters potentially faster. Since we don't have pass through properties I mirrored the default rippleColor from `MDCStatefulRippleView` to match here.
PiperOrigin-RevId: 322585578
Currently we make the ripple the entire size of the button. This limits clients being able to customize if the ripple is inset or outset on a particular side of the button. Since MDCFloatingButton sets its contentEdgeInsets this API is needed to allow for the two values to be independent.
https://developer.apple.com/documentation/uikit/uibutton/1624036-contentedgeinsets
PiperOrigin-RevId: 322199718
Also add visibleAreaInset API to the FAB typical example now that the conflict between visibleAreaInsets and shapeGenerator is resolved.
PiperOrigin-RevId: 315233817
Like the MDCButton, this is opt-in, and the dictionary for the visibleAreaInsets per mode/shape combination is initially empty.
PiperOrigin-RevId: 315152916
This API allows clients to inset the visible content and allow it to be smaller than the frame.
In turn, clients can have a touch target that is bigger than the visible content.
PiperOrigin-RevId: 313556504
The keyword "typeof" is not recognised by the compiler when
using -std=c11 (it is considered a gnu extension). However,
the keyword "__typeof__" is always recognised in both mode (
-std=gnu11 and -std=c11). Thus it is safe to convert to use
"__typeof__" even if building with -std=gnu11.
See https://clang.llvm.org/docs/UsersManual.html#differences-between-various-standard-modes
PiperOrigin-RevId: 306453103
Previously, MDCButton's pointerStyleProvider was ignoring both the proposed effect and proposed shape. To better align with UIButton, we now use the proposed effect and use the button's boundingPath to provide a pointer shape.
PiperOrigin-RevId: 305900307
Note: MDCButton does not enable pointer interactivity by default.
This also adds an example to demonstrate MDCButtons with the default UIPointerInteraction enabled. The example exposes an issue with MDCFloatButton's collapse/expand animations (b/153666859), which will be addressed in a future CL.
PiperOrigin-RevId: 305872547
```
"MDCFloatingButtonModeAnimator.m:150:9: Block implicitly retains 'self'; explicitly mention 'self' to indicate this is intended behavior"
```
This change adds the explicit self. If I got this other people might.
PiperOrigin-RevId: 305777188
TL;DR - This PR consists of fixes for broken links, broken image links, and broken Swift/Objective-C code snippets on material.io, and also adds some small copy edits.
Sometimes our documentation renders okay on GitHub, but breaks in the conversion of markdown to HTML/CSS that takes place during material.io deploys. As of yesterday, I'm able to build material.io locally, which allows me _validate_ the documentation changes I will keep making for the material.io work. It also allows me to catch broken links elsewhere, in totally unrelated files. For example, there were broken links in some Shapes documentation that were already blocking the deployment of our docs unbeknownst to us.
Closes https://github.com/material-components/material-components-ios/pull/9963
COPYBARA_INTEGRATE_REVIEW=https://github.com/material-components/material-components-ios/pull/9963 from andrewoverton:fix-formatting-issues cd54e90863274a49068e016547b1bf0b1af3afcb
PiperOrigin-RevId: 305770167
This snapshot test demonstrates the incorrect behavior of the title label being visible while the button is in normal mode.
PiperOrigin-RevId: 305668064
Two examples were using non-static storage for effectively static consts, causing the symbols to be available available across compilation units and resulting in linker errors when the symbols happen to collide across compilation units.
PiperOrigin-RevId: 305337107
