Open touficbatache opened 7 years ago
After diving into the code, setting needsDeactivationUX
to true fixes the problem. However, the deactivation is not fully complete: you have to click again on the element to make it finish the deactivation process. Could you help @kfranqueiro & @acdvorak ?
I have also come across this issue and it still exists (very noticeable on mobile when scrolling over ripple objects). The codepen above illustrates this easily by using the chrome inspector mobile view and using the touch circle to scroll the list.
Currently the ripple fires immediately after touchstart, pointerdown, mousedown.
The ripple should only fire if the touch is an intentional tap and NOT: touch -> scroll -> release
1) listen for touchdown (set flag 'scroll = false') 2) listen for touchmove (if moved set flag 'scroll = true')
In the referenced codepen I also have the feeling that the ripple activates more than once when "clicking" on a touch device. Is that a result of slightly scrolling it? Or does it just register two taps? It would be great that a ripple couldn't be triggered again for a short period.
(I am not sure how to make a video on the module, any suggestions?)
Hi. Any progress on this?
Bugs
What MDC-Web Version are you using?
What browser(s) is this bug affecting?
What OS are you using?
What are the steps to reproduce the bug?
OR
What is the expected behavior?
What is the actual behavior?