-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update core animate() to allow additional functionality #35
Comments
Yes, there's an open issue that adds the step option so I thought of rewriting it as you say, I'll tackle both asap (bear with me). |
Good to hear! I'm working on something that would benefit from the enhancement but understand these things take time. :) If I come up with anything in the meantime, I'll let you know. |
Thanks, if you get to submit a pull request I'll check it out asap. On Wed, Jan 23, 2013 at 3:43 PM, Peter Hentges notifications@github.comwrote:
Ariel Flesler |
As I commented on another similar issue, found there's a conflict with the "queue" setting which is also recognized by jQuery.animate(). Will look into this. |
This feature is implemented on the window-scroll-alt branch. I created the issue #107 for the whole thing that has a larger scope. |
I merged 2.0.0 to master via #109, the call to |
At its heart, jquery.scrollTo uses this format of the
.animate()
method:Would it be possible to use the alternate version of the
.animate()
method:to allow optional passing in of additional properties that could be animated while the scroll is happening? For example, animating (with the proper plug-ins) the background color of an element while it scrolls.
It appears on cursory examination that this would involve moving the current
duration
,settings.easing
, andcallback
arguments to a newoptions
object as well as getting the currentattr
argument into a newproperties
object along with any other properties that are passed into the plug-in.The text was updated successfully, but these errors were encountered: