Revolution
(Revolution)
September 27, 2014, 12:40pm
1
Please see this video.
It show several timing mis-steps (not sure what to call it).
All 4 element groups share the same core transition - with a small time delay modification.
Organic SEO has a 100 ms time delay.
Local SEO: copy of Organic SEO transition - 300ms
PPC: copy of Local SEO transition - 500ms
Social Network: copy of PPC - 700ms
Can someone tell me what’s happening… I’m guessing the the timers are conflicting with each other ?
Video: http://quick.as/r9arckml
Revolution
(Revolution)
September 27, 2014, 11:29pm
2
no one else has encountered this issue ?
vincent
(Vincent Bidaux)
September 28, 2014, 8:06pm
3
Can you please share your project’s public link so it’s easier to understand your issue?
Learn how to do it here: Share a read-only link | Webflow University
Revolution
(Revolution)
September 29, 2014, 2:00pm
4
vincent
(Vincent Bidaux)
September 29, 2014, 3:49pm
5
I had inconsistant results, can’t say what’s bugging. But I found how to fix, I guess.
Where you have your three part animation, the one going:
wait
scale 1.1 + rotate back origin + opacity 50%
scale 1 + opacity 100%
Then add an extra rotate to origin here:
wait
scale 1.1 + rotate back origin + opacity 50%
scale 1 + rotate back to origin + opacity 100%
Do that on both elements, (compound + button), and test again and tell me.
Revolution
(Revolution)
September 29, 2014, 6:18pm
6
it’s still doing it. element does not rotate to stated point.
thewonglv
(William Wong)
September 29, 2014, 8:07pm
7
Hi @Revolution ,
Thanks for bringing this to our attention. Sorry about the interactions trouble. I’ve verified it as a bug with our ease-in-cubic transition-timing-function and have submitted it to our dev team. Here’s a public link to the recreated issue: https://webflow.com/design/wf-test-canvas-3?preview=87e29e2560cf94925e041c0405574fd6
For now, a possible workaround may be to use “ease” instead (or other transition-timing-functions that are working properly). :-/ I’ll report back as soon as we find a fix for it.
Let me know if you guys have any more trouble with this and if anything changes on your end please update this thread.
Will