[go: up one dir, main page]

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

Stepped easing is not working #881

Closed
doug-kongregate opened this issue Jun 26, 2018 · 9 comments
Closed

Stepped easing is not working #881

doug-kongregate opened this issue Jun 26, 2018 · 9 comments
Assignees
Labels

Comments

@doug-kongregate
Copy link

Your system information

  • VelocityJS version: 2.0.5 via CDN
  • Browser: Firefox, Chrome
  • Operating System: macOS

Please describe your issue in as much detail as possible:

I attempted to animate a selector with stepped easing via the following script:
animator.velocity({ width: 500 }, [ 3 ]);

However, instead of animating in three distinct steps it made a smooth transition from it's initial state to 500px wide.

Steps for reproducing this issue (code):

  1. Assign animation target.
  2. Animate target with a CSS property for a given number of steps as described in the docs.

JSFiddle example showing issue in action (code):

https://jsfiddle.net/51ovg8wh/7/

@Rycochet Rycochet changed the title Stepped easing will not work without JQuery Stepped easing is not working Jun 26, 2018
@Rycochet
Copy link
Collaborator

Changed the title as Velocity V2 has absolutely nothing to do with jQuery at all.

@Rycochet Rycochet added the Bug label Jun 26, 2018
@mrkeyboard
Copy link

As far as I checked, any value in easing, stepped or a simple ease-out etc. isn't working with 2.0.5. All of my animations appear linear -- but maybe I'm using it wrong

@Rycochet Rycochet self-assigned this Jul 8, 2018
@ghost
Copy link
ghost commented Jul 24, 2018

I thought I was the only one having this problem. I thought I was coding it wrong despite putting cubic bezier values since everything appeared linear.

@Rycochet
Copy link
Collaborator

Sorry - I have actually fixed this locally, but it's mixed in with some other things that I'm doing for the release, and I have had absolutely no time to finish that up over the last month or so - things are looking promising for having a few hours over the week though...

@howells
Copy link
howells commented Aug 1, 2018

@Rycochet don't suppose you had a chance to look into this :-)

@Rycochet
Copy link
Collaborator
Rycochet commented Aug 2, 2018

@howells See my comment directly above yours - it's literally a complete lack of time...

@brendan1212
Copy link

@Rycochet Unless I'm missing something, easing is still not functional in beta? I'm concerned that the README is pointing to the wrong version if this is the case. I feel like it might be creating issues for users needing a functional library such as 1.5.1. Please excuse me if I'm mistaken. : )

@Rycochet
Copy link
Collaborator
Rycochet commented May 7, 2019

You are actually mistaken ;-) The only thing stopping v2 from being released is the unfinished testing - once that is done then it will be taken out of beta (technically there's already far more testing than in v1, but it's not up to the standards required for release).

@brendan1212
Copy link
brendan1212 commented May 7, 2019 via email

Rycochet added a commit that referenced this issue Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants