Closed robert4os closed 8 years ago
Ok after a night of sleep. It does not work when the position was not set explicitly before (e.g. "left: 0").
This is the CSS3 'behavior' in Chrome and Forefox, so it is not a specific bug in gwtquery.
However, it is now inconsistent with the Fx.css3=false behavior, which could be fixed, e.g. by setting a default property before the animation.
best regards, Robert
Can you fill an issue in github?
Thanks
On Sat, Jan 25, 2014 at 11:19 AM, robert4os notifications@github.comwrote:
Ok after a night of sleep. It does not work when the position was not set explicitly before (e.g. "left: 0").
This is the CSS3 'behavior' in Chrome and Forefox, so it is not a specific bug in gwtquery.
However, it is now inconsistent with the Fx.css3=false behavior, which could be fixed, e.g. by setting a default property before the animation.
best regards, Robert
— Reply to this email directly or view it on GitHubhttps://github.com/gwtquery/gwtquery/issues/263#issuecomment-33285781 .
Sorry for being slow, but isn't this an issue at github? -Robert
My mistake, I replied this message from my email client, I thought it was a message you sent to the mailing list.
This issue as no activity since more than a year. Feel free to reopen if it is still needed.
For example:
$(container).animate("left:300px", 5000, null);
does not work.
GQuery Version: 1.4.1-SNAPSHOT
// Note it works with Fx.css3=false;