Nobody 266bcd2e07 There are two separate systems trying to manage touch events on the MDCButton. First, the button itself uses its standard UIControl event infrastructure to trigger ink ripples. Second, an external MDCInkTouchController attaches its own gesture recognizers to do the same thing. This creates a conflict where both systems respond to the same touch, causing two ink animations to be created and displayed simultaneously, which results in incorrect visual feedback. ...

PiperOrigin-RevId: 770704081

2025-06-12 10:10:12 -07:00

..

MDCInkLayerTests.m

Add explicit imports for CoreGraphics in files which use it.

2024-06-11 09:16:51 -07:00

MDCInkViewTests.m

There are two separate systems trying to manage touch events on the MDCButton. First, the button itself uses its standard UIControl event infrastructure to trigger ink ripples. Second, an external MDCInkTouchController attaches its own gesture recognizers to do the same thing. This creates a conflict where both systems respond to the same touch, causing two ink animations to be created and displayed simultaneously, which results in incorrect visual feedback.

2025-06-12 10:10:12 -07:00

MDCLegacyInkLayerTests.m

Add explicit imports for CoreGraphics in files which use it.

2024-06-11 09:16:51 -07:00