material-components-ios

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.

Don't pin BottomNavigationBar trailing/leading edges to safe area in horizontal mode.

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...

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.