Should Velocity continue to auto-remove transform values when they hit default values?

Here is what I’m doing:

        $container
            .find('.pfentry__info')
            .velocity('stop')
            .velocity
                properties:
                    opacity: 1
                    scale: [1, 0.9]
                options:
                    display: 'block'
                    duration: 225

I have this in my CSS:

.pfentry__info {
 opacity: 0;
 transform: scale(0.9);
}

When Velocity is run, it scales with forcefeeding from 0.9 to 1, and then it drops scale(1), but keeps opacity: 1.

How do I fix it ? ( a tmp fix would be to remove the transform from CSS, but I’m thinking that this could be a Velocity bug ? )

[MattyBalaam]

As an example if you animate translateY to its default value of ‘0’ you get an inline style left-over ‘transform: translateY(0px);’ Usually this is desired behavior, but the stacking-context as a result of this style can give unwanted results.A previous version of velocity did clear styles when hitting the default, and I wondered if an empty string could be a good way of signalling an intention to clear the style as this is how jQuery’s css function works already.

It seems at the moment I need to clear styles outside of velocity, trying using the hook function with an empty string does nothing. I am worried that in the case of using jQuery’s CSS it will introduce some extra lag - although I am not an expert on the full impact on performance.

[Rycochet]

v1 is now feature locked, so not changing.