fix(ripple): Fix nested ripple handling to work with touch events #2178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reorders code so that the logic that prevents redundant ripple activation from simulated mouse events after a delay on touch devices can function in tandem with the logic which prevents simultaneous activation of nested parent/child ripples.
To see what this fixes, go to list.html, scroll down to the checkbox example, and tap on one of the checkboxes using touch input. The list item should not also ripple at the same time.
I also found and cleaned up a couple of confusing variable declarations (and one excess variable due to one of them).