You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like swiperjs is intercepting the pointercancel event. The browser will dispatch that event when it detects that a user is swiping instead of tapping. When this happens, we end the ripple's animation early.
State is getting mismatched because the pointerup event's pointerId doesn't match the pointerenter's pointerIdhere.
I don't think I'll be able to take a look at swiperjs compatibility unfortunately. Our ripple.shouldReactToEvent() may need tweaks to support swiperjs while also handling the vanilla use case of tapping with multiple pointers.
asyncLiz
changed the title
md-ripple: does not disappear after losing focus/active
md-ripple: does not disappear after losing focus/active with swiperjs
Apr 10, 2024
What is affected?
Component
Description
screen-capture.10.webm
Should the ripple be visible permanently after touch?
Reproduction
Use ripple in some scrollable element
Workaround
.
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
1.4.0
Browser/OS/Node environment
Chrome 123.0.6312.106 (Official Build) (64-bit)
Windows 11
npm 10.2.3
node 20.10.0
The text was updated successfully, but these errors were encountered: