Added resize handling for multiple calls with responsive options (optimized with debouncing) #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nzambello
force-pushed
the
nicola_multipleCallsResponsive
branch
from
87caa70
to
d6025ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm resolving issue #22.
Calling ellipsis - for example - two times with two different selectors, it will handle text even on resize correctly on both node elements.
I also optimized for performance the resize event handling to avoid tons of calls when resizing (while working it freezed): following suggestions well explained here I implemented a debouncing system similar to the underscore.js one.