Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor ripple adding multiple option #691

Merged
merged 2 commits into from Aug 6, 2016
Merged

Refactor ripple adding multiple option #691

merged 2 commits into from Aug 6, 2016

Conversation

javivelasco
Copy link
Member

@javivelasco javivelasco commented Aug 6, 2016

Fixes #305

This PR brings a full refactoring of the Ripple component and a new behavior.

They way it used to work was by restarting the wave if it existed but now you'll have the choice of creating multiple waves. A new option multiple was added to the factory function and also a rippleMultiple property is available for decorated components. If this option is true, instead of restarting the wave, a new wave will be expanded. If the option is false you'll get the same behavior as default.

Since the multiple effect is closer to the spec, it is enabled by default for all components using the ripple. Also, the ripple now supports also onTouchStart so it works perfectly in mobile. Also methods on the ripple has been documented for the future since they are not straightforward.

@javivelasco javivelasco merged commit 75283a5 into dev Aug 6, 2016
@javivelasco javivelasco deleted the 305-multiripple branch August 6, 2016 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ripple effect
1 participant