Skip to content

Fix a race condition where a rapid shrink and expand will cause neither to trigger a change #64

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

Merged
merged 1 commit into from
Sep 16, 2015

Conversation

dustyholmes-wf
Copy link
Contributor

If a user manages to rapidly change both the shrink and expand, then the first one to fire may reset the last width and height causing the other scroll event to fail the change check, incorrectly. By keeping them on separate variables, we prevent this kind of exception.

…er to trigger a change

If a user manages to rapidly change both the shrink and expand, then the first one to fire may reset the last width and height causing the other scroll event to fail the change check, incorrectly. By keeping them on separate variables, we prevent this kind of exception.
marcj added a commit that referenced this pull request Sep 16, 2015
Fix a race condition where a rapid shrink and expand will cause neither to trigger a change
@marcj marcj merged commit 921e954 into marcj:master Sep 16, 2015
@marcj
Copy link
Owner

marcj commented Sep 16, 2015

thanks, good catch!

@jyrkij
Copy link

jyrkij commented Oct 1, 2015

Was this reverted by c16cdc9?

@marcj
Copy link
Owner

marcj commented Oct 1, 2015

Yes, see PR description at #65

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.

3 participants