This release includes major performance improvements and a new animation engine.
Beware of the breaking change with
.up-current on all links turned out to be a major performance bottleneck, so we had to make some breaking changes:
.up-currentclass is now only assigned to links with an
[up-nav]attribute, or to links within a container with an
[up-nav]attribute. You should assign the
[up-nav]attribute to all navigational elements that rely on
You can also globally configure selectors for your navigational elements in
[up-nav]links are now cached for performance reasons.
[up-nav]links are only updated once when multiple fragments are updated in a single replacement.
up.motion.config.enabled = false.
up.morph()will now expect the new fragment version to be detached from the DOM before morphing.
up.morph()will now detach the old fragment version from the DOM after morphing.
up.morph()function has been demoted from stable to experimental.
up.motion.finish()now longer queries the DOM when there are no active animations.
documentto be the viewport.
up:fragment:destroyedevent is now emitted after the fragment has been removed from the DOM. The event is emitted on the former parent of the removed fragment.
truefor a function value
up.util.only()did not copy properties inherited from a prototype