Ryc O'Chet

I've been hit by this bug too - on a related note, `text.cacheAsBitmap` is not being respected, so you can't bypass it that way :-/

> Hi any chance that the video is set to public again? Sorry, I don't know who that was created by, and have no control over it, @julianshapiro any clue?

Not sure what's going on with your setup, but the code quite literally cannot do that - it attaches to everything it can in order, and there is no branching...

As a User v2 and v3 will remain almost identical - only if creating sequences, easings, or similar extensions to Velocity would there need to be any code changes -...

> Any news here available in the meanwhile? > With best regards Sadly not - with no time / energy for any more, I have local changes that are part-way...

This may be related to #881 where the easings are not running correctly - as soon as I get time to push that (it's mixed with other unfinished changes) then...

Thanks for the Fiddle, lets me see a bit better - looks like the `translate3d(0,-100,0)` is getting changed to `translate3d(,-100,)` which is breaking it, furthermore it's set to `display:inline` so...

@Frohmen Separate out the relevant code into a JSFiddle, then if it should be working as per the Wiki at the top of the page open a bug report, otherwise...

And you've just shown you haven't read any release notes or documentation - `tried with translateX`...

https://github.com/julianshapiro/velocity/blob/master/V2_CHANGES.md > Transforms - Use these directly within CSS, don't try the old shortcuts as they don't exist. https://github.com/julianshapiro/velocity/blob/master/CONTRIBUTING.md > Unless you're reporting an obvious bug that can be immediately...