change in the way Element.prototype.fade overloads arguments to Fx.Tween #2125

DimitarChristoff opened this Issue Nov 16, 2011 · 2 comments


None yet
2 participants

DimitarChristoff commented Nov 16, 2011

This is one of these undocumented features that I have always taken for granted:

element.fade(0, 1); behaviour has changed in 1.4

previously, the switch statement would pass on all arguments to the Fx.Tween instance so the above would work:

now, the default on the switch reverts to working with a single argument only (how), which means you cannot set the start value of the tween, only the end one.

The old behaviour was rather nice, it provided an Element shortcut API into Fx.Tween, can it be reverted back, please as it's a breaking change that is not warranted by any real concern.

arian added a commit to arian/mootools-core that referenced this issue Nov 16, 2011


arian commented Nov 16, 2011

See pull #2126


DimitarChristoff commented Nov 16, 2011

thanks so much! awesome.

arian added a commit to ibolmo/mootools-core that referenced this issue Dec 20, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment