Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
Update README.md
5.0.0

“In” transitioning elements have their initial opacity set to 0
immediately (instead of waiting for the first rAF tick). This removes
FOUC. Closes #248.

New Sequence Running feature. See: http://velocityjs.org/#uiPack.
Thanks @stephen. Closes #296.
1.1.0
1.1.0
5.0.0

Implements #288. Thanks @imrefazekas.
1.1.0

Internal “Sequences” have been renamed to “Redirects”. You shouldn’t
have been using them (they were deprecated), so this is not being
considered backwards-incompatible.

`Velocity.mock` now accepts a multiplier value in addition to `true`.
Use it for slowing down/speeding up animations globally when testing.
`true` mock has also been fixed to also reduce `delay`s to 1ms.

You can now animate `filter: blur(value);` for -webkit- browsers. Note
that animating this property will strip out all other `filter`
components. Note that, at the time of this update, Chrome incorrectly
returns blur values that were originally set with the `px` unit.

`color` RGB defaults to black instead of white, which is closer to
text’s typical color value.

`opts.progress` now gets repeatedly fired during looped calls. Closes
#292.

Fix jQuery-free `position: absolute` bug with left/top properties.
Closes #285.

Allow passing undefined as a second arg into Velocity. Closes #275.

Performance improvement: Individual property tweens don’t update the
DOM if there’s no change in value between loop ticks.

Fixes bug where `loop`ing on iOS devices (due to mobileHA) would cause
flickering. Closes #299.

Fixes bug where you couldn’t force-feed one hex value to another.

Can now set `visibility: “”`, just like you can with display.

Fixed bug where using `backwards: true:` with the UI pack mutated the
source array.
5.0.0

Fix module loading issue. Closes #288.
Update bower.json
Update package.json
Update README.md