Skip to content

Latest commit

 

History

History
2150 lines (1403 loc) · 96.2 KB

CHANGELOG.md

File metadata and controls

2150 lines (1403 loc) · 96.2 KB
Raw

Changelog

Changes to this project will be documented in this file.

You may browse a formatted and hyperlinked version of this file at https://unpoly.com/changes.

0.60.3

[up-validate] again recognizes the [up-fieldset] attribute to find the form fragment that should be replaced with validation results.

In the example below, changing the email input would only validate the first fieldset:

<form action="/users" id="registration">

  <div up-fieldset>
    Validation message
    <input type="text" name="email" up-validate />
  </div>

  <div up-fieldset>
    Validation message
    <input type="password" name="password" up-validate />
  </div>

</form>

0.60.2

  • When submitting a form with a GET method, any query parameters in the form's [action] URL are now discarded. This matches the standard browser behavior when submitting a form without Unpoly.
  • When submitting a form with a POST method, any query parameters in the form's [action] URL are now kept in the URL, instead of being merged into the form's data payload. This matches the standard browser behavior when submitting a form without Unpoly.
  • New experimental function up.Params.stripURL(url). It returns the given URL without its query string.

0.60.1

0.60.0

This is a major update with some breaking changes.

Highlights

  • jQuery is no longer required! Unpoly now has zero dependencies.
  • New up.element helpers to complement native Element methods. You might not even miss jQuery anymore.
  • Vastly improved performance on slow devices.
  • Utility functions that work with arrays and array-like values have been greatly improved.
  • The up.util module now plug the worst emissions in JavaScript's standard library: Equality-by-value, empty-by-value and shallow-copy. Your own objects may hook into those protocols.
  • You may define a padding when revealing.
  • Smooth scrolling now mimics native scroll behavior.
  • Fixed many positioning issues with popups and tooltips.
  • Several modules have been renamed to match the pattern up.thing.verb(). up.dom is now up.fragment, up.bus is now up.event, up.layout is now up.viewport.

Details below.

jQuery is no longer required

jQuery no longer required to use Unpoly. That means Unpoly no longer has any dependencies!

Due to its use of native DOM APIs, Unpoly is now a lot faster. Like, a lot. Ditching jQuery also saves you 30 KB of gzipped bundle size and speeds up your own code.

Migrating apps that use jQuery

Effort has been made to ensure that migrating to this version is smooth for existing apps that use jQuery.

All Unpoly functions that accept element arguments will accept both native elements and jQuery collections.

You will need to prefix some function calls with $ to have your callbacks called with jQuery collections instead of native elements:

  • The up.compiler() callback now receives a native element instead of a jQuery collection. For the old behavior, use up.$compiler().
  • The up.macro() callback now received a native element instead of a jQuery collection. For the old behavior, use up.$macro().
  • The event handler passed to up.on() now receives an element instead of a jQuery collection. For the old behavior, use up.$on().

Finally, all Unpoly events (up:*) are now triggered as native events that can be received with Element#addEventListener(). You may continue to use jQuery's jQuery#on() to listen to Unpoly events, but you need to access custom properties through event.originalEvent.

Also know that if you use jQuery's $.fn.trigger() to emit events, these events are not received by native event listeners (including Unpoly). Use up.emit() instead to trigger an event that can be received by both native listeners and jQuery listeners.

See below for detailed changes.

New DOM helpers

A new, experimental up.element module offers convience functions for DOM manipulation and traversal.

It complements native Element methods and works across all supported browsers without polyfills.

| up.element.first() | Returns the first descendant element matching the given selector.| | up.element.all() | Returns all descendant elements matching the given selector.| | up.element.subtree() | Returns a list of the given parent's descendants matching the given selector. The list will also include the parent element if it matches the selector itself.| | up.element.closest() | Returns the first element that matches the selector by testing the element itself and traversing up through its ancestors in the DOM tree.| | up.element.matches() | Matches all elements that have a descendant matching the given selector.| | up.element.get() | Casts the given value to a native Element.| | up.element.toggle() | Display or hide the given element, depending on its current visibility.| | up.element.toggleClass() | Adds or removes the given class from the given element.| | up.element.hide() | Hides the given element.| | up.element.show() | Shows the given element.| | up.element.remove() | Removes the given element from the DOM tree.| | up.element.replace() | Replaces the given old element with the given new element.| | up.element.setAttrs() | Sets all key/values from the given object as attributes on the given element.| | up.element.affix() | Creates an element matching the given CSS selector and attaches it to the given parent element.| | up.element.createFromSelector() | Creates an element matching the given CSS selector.| | up.element.createFromHtml() | Creates an element from the given HTML fragment.| | up.element.toSelector() | Returns a CSS selector that matches the given element as good as possible.| | up.element.setAttrs() | Sets all key/values from the given object as attributes on the given element.| | up.element.booleanAttr() | Returns the value of the given attribute on the given element, cast as a boolean value.| | up.element.numberAttr() | Returns the value of the given attribute on the given element, cast to a number.| | up.element.jsonAttr() | Reads the given attribute from the element, parsed as JSON.| | up.element.style() | Receives computed CSS styles for the given element.| | up.element.styleNumber() | Receives a computed CSS property value for the given element, casted as a number.| | up.element.setStyle() | Sets the given CSS properties as inline styles on the given element.| | up.element.isVisible() | Returns whether the given element is currently visible.| | :has() | A non-standard pseudo-class that matches all elements that have a descendant matching the given selector. |

Events

  • The up.bus module has been renamed to up.event. We want to normalize Unpoly's API to the pattern up.thing.verb() in the future.

  • All Unpoly events (up:*) are now triggered as native events that can be received with Element#addEventListener(). You may continue to use jQuery's jQuery#on() to listen to Unpoly events, but you need to access custom properties from event.originalEvent.

  • Properties named event.$target and event.$element have been removed from all Unpoly events. Use the standard event.target to retrieve the element on which the element was emitted.

  • up.on() may now bind to a given element by passing it as an (optional) first argument:

    up.on(element, '.button', 'click', (event) => { ... })

    You may use this for event delegation.

  • The event handler passed to up.on() now receives an element instead of a jQuery collection:

    up.on('click', (event, element) => {
  alert("Clicked on an " + element.tagName)
})

    For the old behavior, use up.$on().

  • up.emit() may now trigger an event on a given element by passing the element as an (optional) first argument:

    up.emit(element, 'app:user:login', { email: '[email protected]' })

  • up.emit() option { message } is now { log }.

  • up.emit() no longer logs by default. You can enable the old efault message with { log: true }.

  • up.event.nobodyPrevents() option { message } is now { log }.

  • The experimental function up.reset() was removed without replacement.

  • The experimental event up:framework:reset was removed without replacement.

Custom JavaScript

  • Compilers may again return an array of destructor functions. The previous deprecation was removed.

  • The up.compiler() callback now receives a native element instead of a jQuery collection:

    up.compiler('.button', function(button) {
  alert("We have a new button with class " + button.className)
})

    For the old behavior, use up.$compiler().

  • The up.macro() callback now received a native element instead of a jQuery collection:

    up.compiler('a.fast-link', function(element) {
  element.setAttribute('up-preload', 'up-preload')
  element.setAttribute('up-instant', 'up-instant')
})

    For the old behavior, use up.$macro().

Forms

  • up:form:submit no longer has a { $form } property. The event is now emitted on the form that is being submitted.

  • up.observe() now accepts a single form field, multiple fields, a <form> or any container that contains form fields. The callback is called once for each change in any of the given elements.

  • The callback for up.observe() now receives the arguments (value, name), where value is the changed field value and name is the [name] of the field element:

    up.observe('form', function(value, name) {
  console.log('The value of %o is now %o', name, value);
});

    The second argument was previously the observed input element as a jQuery collection.

  • up.observe() now accepts a { batch: true } option to receive all changes since the last callback in a single object:

    up.observe('form', { batch: true }, function(diff) {
  console.log('Observed one or more changes: %o', diff);
});

  • The default up.form.config.validateTargets no longer includes the selector '[up-fieldset]'.

Animation

  • CSS property names for custom animations and transitions must be given in kebab-case. camelCase properties are no longer supported.

Fragment update API

  • The module up.dom has been renamed to up.fragment. We want to normalize Unpoly's API to the pattern up.thing.verb() in the future.
  • The experimental function up.all() has been removed without replacement
  • The function up.first() has been renamed to up.fragment.first() to not be confused with the low-level up.element.first().
  • The event up:fragment:destroy has been removed without replacement. This event was previously emitted before a fragment was removed. The event up:fragment:destroyed (emitted after a fragment was removed), remains in the API.
  • The up:fragment:destroyed event no longer has a { $element } property. It now has a { fragment } property that contains the detached element. Like before, it is emitted on the former parent of the destroyed element.
  • The properties for the up:fragment:keep event have been renamed.
  • The properties for the up:fragment:kept event have been renamed.
  • The properties for the up:fragment:inserted event have been renamed.
  • The properties for the up:fragment:destroyed event have been renamed.

Utility functions

The up.util module now plug the worst emissions in JavaScript's standard library: Equality-by-value, empty-by-value, shallow copy:

  • New experimental function up.util.isEqual(). It returns whether the given arguments are equal by value.
  • New experimental property up.util.isEqual.key. This property contains the name of a method that user-defined classes may implement to hook into the up.util.isEqual() protocol.
  • up.util.isBlank() now returns false for objects with a constructor.
  • New experimental property up.util.isBlank.key. This property contains the name of a method that user-defined classes may implement to hook into the up.util.isBlank() protocol.
  • New experimental property up.util.copy.key. This property contains the name of a method that user-defined classes may implement to hook into the up.util.copy() protocol.

More utility functions to have been added to work with lists:

  • New experimental function up.util.findResult(). It consecutively calls the given function which each element in the given list and returns the first truthy return value.
  • New experimental function up.util.flatten(). This flattens the given list a single level deep.
  • New experimental function up.util.flatMap(). This maps each element using a mapping function, then flattens the result into a new array.

Some list functions have been renamed to names used in the standard Array API:

  • up.util.all() was renamed to up.util.every() to match the standard Array#every(), and to be less confusing with up.element.all().
  • up.util.any() was renamed to up.util.some() to match the standard Array#some().
  • up.util.select() was renamed to up.util.filter() to match the standard Array#filter().
  • up.util.detect() was renamed to up.util.find() to match the standard Array#find().

All functions that worked for arrays now also work for array-like values:

  • New experimental function up.util.isList(). It returns whether the given argument is an array-like value, like an Array or a NodeList.
  • up.util.reject() now works for all array-like values, not just arrays.
  • up.util.filter() now works for all array-like values, not just arrays.
  • up.util.find() now works for all array-like values, not just arrays.
  • up.util.some() now works for all array-like values, not just arrays.
  • up.util.every() now works for all array-like values, not just arrays.

And some minor changes:

  • up.util.nextFrame() has been renamed to up.util.task().
  • up.util.setTimer() has been renamed to up.util.timer().
  • `up.util.toArray() now returns its unchanged argument if the argument is already an array.
  • up.util.copy() now works with Date objects.
  • up.util.isBoolean() is now stable
  • up.util.escapeHtml() is now stable
  • up.util.isJQuery() now returns false if no jQuery is loaded into the window.jQuery global
  • up.util.unresolvablePromise() was removed without replacement.
  • up.util.trim() has been removed without replacement. Use the standard String#trim() instead.
  • up.util.parseUrl() now returns the correct { hostname }, { protocol } and { pathname } properties on IE11.
  • up.util.selectorForElement() is now up.element.toSelector()

Scrolling Viewports

  • The up.layout module has been renamed to up.viewport. We want to normalize Unpoly's API to the pattern up.thing.verb() in the future.
  • Smooth scrolling now mimics native scroll behavior:
    • up.scroll() no longer takes a { duration } or { easing } option.
    • up.scroll() now takes a { behavior } option. Valid values are auto (no animation) and smooth (animates the scroll motion).
    • You may control the pace of { behavior: 'smooth' } by also passing a { speed } option`.
    • New config property up.viewport.scrollSpeed. This sets the default speed for smooth scrolling. The default value (1) roughly corresponds to the default speed of Chrome's native smooth scrolling.
  • Options for up.reveal() have been changed:
    • Options { duration } and { easing } have been removed.
    • New option { padding } to pass the desired padding between the revealed element and the closest viewport edge (in pixels).
    • New option { snap }. It can be true, false or a pixel number.
    • New option { behavior }
    • New option { speed }. Defaults to up.viewport.scrollSpeed.
    • Config property up.layout.config.snap has been renamed to up.viewport.config.revealSnap.
    • New config option up.viewport.revealPadding.
  • New experimental function up.viewport.root(). It return the scrolling element for the browser's main content area.
  • New experimental function up.viewport.closest(). It returns the scrolling container for the given element.
  • When a #hash anchor is revealed during the initial page load, Unpoly will look for an [up-id=hash] before looking for [id=hash] and a[name=hash].
  • Fix issues with restoring scroll positions when going back on some browsers.

Navigation feedback

  • [up-alias] now accepts one or more asterisks (*) anywhere in the pattern. It was previously limited to match URLs with a given prefix.

Performance

  • Use of native browser APIs has improved performance drastically.
  • [up-preload] and [up-instant] links no longer bind to the touchstart event, increasing frame rate while scrolling.

Request parameters

The experimental up.params module has been replaced with the up.Params class. Wrap any type of parameter representation into up.Params to get consistent API for reading and manipulation.

The following types of parameter representation are supported:

  1. An object like { email: '[email protected]' }
  2. A query string like 'email=foo%40bar.com'
  3. An array of { name, value } objects like [{ name: 'email', value: '[email protected]' }]
  4. A FormData object. On IE 11 and Edge, FormData payloads require a polyfill for FormData#entries().

Supported methods are:

| new up.Params() | Constructor. | | up.Params#add() | Adds a new entry with the given name and value. | | up.Params#addAll() | Adds all entries from the given list of params. | | up.Params#addField() | Adds params from the given HTML form field. | | up.Params#delete() | Deletes all entries with the given name. | | up.Params#get() | Returns the first param value with the given name from the given params. | | up.Params#set() | Sets the value for the entry with given name. | | up.Params#toArray() | Returns an array representation of this up.Params instance. | | up.Params#toFormData() | Returns a FormData representation of this up.Params instance. | | up.Params#toObject() | Returns an object representation of this up.Params instance. | | up.Params#toQuery() | Returns an query string for this up.Params instance. | | up.Params#toURL() | Builds an URL string from the given base URL and this up.Params instance as a query string. | | up.Params.fromFields() | Constructs a new up.Params instance from one or more HTML form field. | | up.Params.fromForm() | Constructs a new up.Params instance from the given <form>. | | up.Params.fromURL() | Constructs a new up.Params instance from the given URL's query string. |

Popups

  • The HTML markup for a popup has been changed to make it easier to style with CSS. The new structure is:

    <div class="up-popup">
  <div class="up-popup-content">
    Fragment content here
  </div>
</div>

  • The default CSS styles for .up-popup has been changed. If you have customized popup styles, you should check if your modifications still work with the new defaults.

  • Popups now update their position when the screen is resized.

  • Popups now follow scrolling when placed within viewports other than the main document.

  • The [up-position] attribute has been split into two attributes [up-position] and [up-align]. Similarly the { position } option has been split into two options { position } and { align }:

    • { position } defines on which side of the opening element the popup is attached. Valid values are 'top', 'right', 'bottom' and 'left'.
    • { align } defines the alignment of the popup along its side.
    • When the popup's { position } is 'top' or 'bottom', valid { align } values are 'left', center' and 'right'.
    • When the popup's { position } is 'left' or 'right', valid { align } values are top', center' and bottom'.

  • New experimental function up.popup.sync(). It forces the popup to update its position when a layout change is not detected automatically.

  • popup elements are now appended to the respective viewport of the anchor element. They were previously always appended to the end of the <body>.

  • The events up:popup:open,up:popup:opened, up:popup:close and up:popup:closed have an { anchor } property. It references the element that the popup was attached to.

Tooltips

  • The HTML markup for a popup has been changed to make it easier to style with CSS. The new structure is:

    <div class="up-tooltip">
  <div class="up-tooltip-content">
    Tooltip text here
  </div>
</div>

  • The default CSS styles for .up-tooltip have been changed. If you have customized tooltip styles, you should check if your modifications still work with the new defaults.

  • Tooltips now update their position when the screen is resized.

  • Tooltips now follow scrolling when placed within viewports other than the main document.

  • The [up-position] attribute has been split into two attributes [up-position] and [up-align]. Similarly the { position } option has been split into two options { position } and { align }:

    • { position } defines on which side of the opening element the popup is attached. Valid values are 'top', 'right', 'bottom' and 'left'.
    • { align } defines the alignment of the popup along its side.
    • When the tooltip's { position } is 'top' or 'bottom', valid { align } values are 'left', center' and 'right'.
    • When the tooltip's { position } is 'left' or 'right', valid { align } values are top', center' and bottom'.

  • New experimental function up.tooltip.sync(). It forces the popup to update its position when a layout change is not detected automatically.

  • Tooltip elements are now appended to the respective viewport of the anchor element. They were previously always appended to the end of the <body>.

Ruby on Rails integration

AJAX acceleration

  • The properties for the up:link:preload event have been renamed.

Modal dialogs

  • Opening/closing a modal will now manipulate the { overflow-y } style on the same element that was chosen by the CSS author (nasty details).

Various

  • Renamed some files so they won't be blocked by over-eager ad blockers on developer PCs.
  • Deprecation warnings are only printed once per environment.

0.57.0

Request parameters

To prevent confusion with [up-data], Unpoly now uses the word "params" when talking about form values or request parameters:

  • up.request() option { data } has been renamed to { params }.
  • up.replace() option { data } has been renamed to { params }.

Parameters may be passed in one of the following types:

  1. an object like { email: '[email protected]' }
  2. a FormData object
  3. a query string like email=foo%40bar.com
  4. an array of { name, value } objects like [{ name: 'email', value: '[email protected]' }]

To help working with form values and request parameters, an experimental module up.params has been added. It offers a consistent API to manipulate request parameters independent of their type.

Application layout

  • When Unpoly cannot find the viewport of an element, it now uses the scrolling root element. This is either <body> or <html>, depending on the browser.
  • Fix a bug where linking back and forth between multiple #anchor hashes of the same URL would always reveal the first anchor.
  • Revealing elements below fixed navigation bars now honors the navigation bar's padding, border, margin, top and bottom properties.
  • Fix a bug where revealing elements fixed navigation bars would scroll 1 pixel too short.
  • up.layout.revealHash() no longer retrieves the hash anchor from the current URL. You need to pass in a #hash value as a first argument.
  • Fix a bug where a #hash anchor would not be revealed if it included non-word characters like spaces or dots.

Compilers

  • To improve performance, Unpoly no longer parses [up-data] attributes when a compiler function does not require a second data argument.
  • Compilers that return destructor functions now run slightly faster.
  • Compilers with { batch: true } now receive an array of [up-data] objects as their second data argument.
  • Compilers with { batch: true } can no longer return destructor functions. Previously the behavior of batch destructors was undefined, now it throws an error.
  • Returning an array of destructor functions from up.compiler() is now deprecated. Please return a single destructor function instead.
  • up.syntax.data() now returns undefined if the given object has no (or an empty) [up-data] attribute. It previously returned an empty object.

Event listeners

  • To improve performance, Unpoly no longer parses [up-data] attributes when an up.on() listener does not require a third data argument.
  • up.on() now throws an error when the same callback function is registered multiple times.

Fragment update API

Various

0.56.7

  • Calling event.preventDefault() on up:modal:close and up:popup:close events no longer prints Uncaught (in promise) to the error console. You still need to catch rejected promises in your own code when it calls Unpoly functions and that function is prevented by an event handler.

0.56.6

  • Fix a regression where the contents of <noscript> tags were parsed into DOM elements (instead of text) when a fragment contained more than one <noscript> element. Thanks to @foobear for helping with this.

0.56.5

  • Fix a bug where loading a page with both a ?query string and a #fragment hash would throw an error

0.56.4

  • Improve performance of HTML parsing.

0.56.3

  • Fix a bug where the Bootstrap 3 integration failed to load. Thanks @dastra-mak!

0.56.2

0.56.1

  • New stable selector .up-destroying. This CSS class is assigned to elements before they are destroyed or while they are being removed by a transition.
  • Fix a bug where up.first() would sometimes find an element that is being destroyed.

0.56.0

This release includes major performance improvements and a new animation engine.

Beware of the breaking change with .up-current!

Navigation feedback

Maintaining the .up-current on all links turned out to be a major performance bottleneck, so we had to make some breaking changes:

  • The .up-current class 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 .up-current for styling`.

  • You can also globally configure selectors for your navigational elements in up.feedback.config.navs:

    up.feedback.config.navs.push('.my-nav-bar')

  • The normalized URLs of [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.

Animation

  • When performing an animated page transition Unpoly will no longer create copies of the old and new fragment versions. The animation will instead be performed on the fragment elements themselves.
  • When animating an element with an existing CSS transition, Unpoly will now pause the CSS transition in its current state, perform the animation, then resume the CSS transition.
  • Unpoly now does less work when animation is disabled globally through 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.
  • The up.morph() function has been demoted from stable to experimental.
  • up.motion.finish() now longer queries the DOM when there are no active animations.

Application layout

  • When Unpoly cannot find the viewport of an element, it will now always considers document to be the viewport.

Fragment updates

  • The up:fragment:destroyed event is now emitted after the fragment has been removed from the DOM. The event is emitted on the former parent of the removed fragment.

Utility functions

General

  • Partially remove jQuery from internal code for performance reasons. We want to eventually remove jQuery as a dependency.
  • Cache the results of feature detection for performance reasons.
  • Unpoly is now more efficient when selecting elements from the DOM.
  • Unpoly is now more efficient when reacting to mouse events.

0.55.1

This release restores support for Internet Explorer 11, which we accidentally broke in 0.55.0.

Thanks to @foobear for helping with this.

0.55.0

Fragment updates

  • Unpoly now detects when an [up-target] with multiple selectors would replace the same element multiple times. In such a case the target selector will be shortened to contain the element once.
  • Unpoly now detects when an [up-target] with multiple selectors contains nested elements. In such a case the target selector will be shortened to only contain the outmost element.

Utility functions

  • up.util.uniq() now works on DOM elements and other object references.
  • New experimental function up.util.uniqBy(). This function is like uniq, accept that the given function is invoked for each element to generate the value for which uniquness is computed.
  • Changes to utility functions that work on lists (up.util.each(), up.util.map(), up.util.all(), up.util.any(), up.util.select(), up.util.reject()):

    • List functions now accept a property name instead of a mapping function:

      users = [{ name: 'foo' }, { name: 'bar' }]
up.util.map(users, 'name') // ['foo', 'bar']

    • List functions now pass the iteration index as a second argument to the given function:

      users = [{ name: 'foo' }, { name: 'bar' }]
up.util.map(users, function(user, index) { return index }) // [0, 1]

0.54.1

This release contains no new features, but will help you when using tools like Babel or Webpack:

  • Unpoly now ship without any uses of eval() in its JavaScript sources. Use of eval() had previously prevented minifiers from shortening local variables in some files.
  • Documentation in Unpoly's JavaScript sources can no longer be confused with JSDoc comments. Unpoly does not use JSDoc, but some build pipelines eagerly look for JSDoc comments to generate type information.

0.54.0

Passive updates

  • [up-hungry] elements will now also be updated when the server responds with an error code. This helps when [up-hungry] is used to display error messages.

Forms

  • When a form is submitted you can now consistently refer to that form element as & in CSS selectors (like in Sass).

    E.g. to reveal the first error message within a failed form submission:

    <form id="my-form" up-target=".page" up-fail-reveal="& .error">
  ...
</form>

    In this case & .error will be replaced by #my-form .error before submission.

    This affects CSS selectors in the following HTML attributes:

    • form[up-target]
    • form[up-fail-target]
    • form[up-reveal]
    • form[up-fail-reveal]

Linking to fragments

  • When a link is followed you can now consistently refer to that link element as & in CSS selectors (like in Sass).

    This affects CSS selectors in the following HTML attributes:

    • a[up-target]
    • a[up-fail-target]
    • a[up-reveal]
    • a[up-fail-reveal]

Fragment update API

0.53.4

Passive updates

  • Updates for [up-hungry] elements will no longer auto-close a modal dialog.
  • Updates for [up-hungry] elements will no longer auto-close a popup overlay.
  • CSRF-related <meta> tags are no longer updated automatically with every request. This is to prevent unnecessary DOM jitter in applications that don't rotate CSRF tokens.

Popup overlays

  • Calling up.popup.attach() without a target selector will now throw an error.

0.53.2

General

  • Failed requests in event handlers of CSS selectors like form[up-target] no longer print Uncaught (in promise) to the error console. You still need to catch and handle rejected promises in your own code when it calls Unpoly functions.

Animated transitions

  • Fix a bug where a page transition would flicker if revealing was animated globally by setting up.layout.config.duration.

Preloading

0.53.1

General

  • Fix a bug where replacing the first element on the page (in DOM order) would shift the scroll position if animation is disabled.
  • Fix a bug where query params would be lost when Unpoly would fall back to a full page load.

Optional server protocol

Animations

  • Fix a bug where the animation move-from-top would finish instantly after animating with move-to-top.
  • Fix a bug where the animation move-from-right would finish instantly after animating with move-to-right.
  • Fix a bug where the animation move-from-bottom would finish instantly after animating with move-to-bottom.
  • Fix a bug where the animation move-from-left would finish instantly after animating with move-to-left

0.53.0

New module: Passive updates

Thi work-in-progress package up.radio will contain functionality to passively receive updates from the server. Currently the following functionality is implemented:

  • Elements with an [up-hungry] attribute are updated whenever there is a matching element found in a successful response. The element is replaced even when it isn't targeted directly.

    Use cases for this are unread message counters or notification flashes. Such elements often live in the layout, outside of the content area that is being replaced.

  • When a reserver response contains a <meta name="csrf-param"> or <meta name="csrf-token"> element, it is automatically updated in the current page.

General

  • Changes when generating CSS selectors for elements:
    • [aria-label] attributes are used if no better attributes exist (like [id] or [up-id] attributes).
    • Attribute values with quotes are now escaped if they appear in an attribute selector.
    • Attribute selectors now use double quotes instead of single quotes.
    • When a [name] attribute is used, the tag name is also used. E.g. meta[name="csrf-token"].
    • Element IDs that contain non-word characters (e.g. slashes, spaces, dots), will now generate an attribute selector like [id="foo/bar"].

Forms

  • You can give forms an [up-fail-reveal] attribute to indicate which element should be revealed when the server responds with an error. You may use this, for example, to reveal the first validation error message: 
    <form up-target=".content" up-fail-reveal=".error">
  ...
</form>
  • Forms with an [up-reveal] attribute will now only honor the attribute when the form submission was successful.
  • Forms with an [up-restore-scroll] attribute will now only honor the attribute when the form submission was successful.
  • Forms with an [up-reveal="css-selector"] attribute will no longer crash when the selector could not be found.
  • Fix a bug where you couldn't submit a form if it's ID contains a slash character (#46).

Links

  • You can give links an [up-fail-reveal] attribute to indicate which element should be revealed when the server responds with an error
  • Links with an [up-reveal] attribute will now only honor the attribute when the link could be followed successfully.
  • Links with an [up-restore-scroll] attribute will now only honor the attribute when the link could be followed successfully.
  • Links with an [up-reveal="css-selector"] attribute will no longer crash when the selector could not be found.

Animations

  • When replacing multiple elements, it is no longer possible to use different transitions for each element. The same transition is always applied to all elements.

0.52.0

Browser support

  • No longer prints an error to console when registering a macro on an unsupported browser.

AJAX requests

  • Unpoly can now detect the final URL of a redirect response without the optional server protocol. The server protocol is still needed to detect redirects on Internet Explorer 11.
  • When making HTTP requests Unpoly will now always merge params in the URL's query section with params from the { data } option.

Forms

Forms

0.51.1

Fragment updates

  • Fix a bug where Unpoly would crash when replacing a fragment with a <script> tag with a later sibling element.

0.51.0

Fragment updates

  • <script> tags that were inserted by a fragment update are no longer executed. They are still executed during the initial page load. If you need a fragment update to call JavaScript code, call it from a compiler (Google Analytics example).
  • The configuration option up.dom.config.runInlineScripts has been removed without replacement.
  • The configuration option up.dom.config.runLinkedScripts has been removed without replacement.
  • Fix a bug where the contents of <noscript> tags were parsed into DOM elements (instead of a single verbatim text node). This was confusing libraries that work with <noscript> tags, such as lazysizes.
  • Work around a bug in IE11 and Edge where <noscript> tags that were inserted by a fragment update could not be found with jQuery or document.querySelectorAll().

0.50.2

Fragment updates

  • Updating fragments is now much faster when no [up-keep] elements are involved.

Scrolling

  • up.reveal() no longer crashes when called with a CSS selector or non-jQuery element.
  • up.reveal() now returns a rejected promise when no viewport could be found for the given element.

Links

  • [up-expand] now ignores clicks on form fields. This is useful e.g. when up-expanding a table row that contains both links and form fields.

Network

  • a[up-preload] will no longer preload a link when the user holds the Shift, Ctrl or Meta key while hovering.

0.50.1

General

  • Boolean HTML attributes are now also considered true if their values equal the attribute name, e.g. up-keep="up-keep" (#36)

AJAX

  • up.request() now sends an X-Requested-With: XMLHttpRequest headers. This header is used by many server-side frameworks to detect an AJAX request. (#42)

0.50.0

This is a major update with some breaking changes. Expect a few more updates like this as we move closer to our 1.0 release in 2018.

General

  • jQuery 3 is now supported in addition to jQuery 1.9+ and jQuery 2.
  • Unpoly now uses native Promises instead of jQuery deferreds.
  • You can now help improve Unpoly's documentation by clicking an Edit this page link on any unpoly.com subpage (like a[up-target]).

Browser support

  • To enable support for Internet Explorer 11 you need to install a Polyfill for Promise. We recommend ES6-promise (2.4 KB gzipped).
  • Fix a bug where Unpoly would not boot on Safari 9 and 10 if the initial page was loaded with a POST method.

AJAX

  • Unpoly now uses native XMLHttpRequest instead of jQuery.ajax(). If you have been hacking into Unpoly's networking through jQuery.ajaxPrefilter(), you must now use the up:proxy:load event.
  • up.ajax() has been deprecated since its signature is incompatible with native promises. Please use up.request() instead, whose promise fulfills with an up.Response object.
  • The up:proxy:received event has been renamed to up:proxy:loaded.
  • The up:proxy:load event properties have changed. You can now access request properties through a key { request }, e.g. event.request.url.
  • The up:proxy:load event can now be prevented to prevent a request from being sent to the network.
  • The up:proxy:load event now allows listeners to change request headers by manipulating the event.request.headers object.
  • A new event up:proxy:fatal will be emitted when an AJAX request encounters fatal error like a timeout or loss of network connectivity.

Links

  • Links with unsafe HTTP methods like POST are no longer marked as .up-current, even if their [href] matches the current URL.
  • New experimental function up.link.isSafe(). It returns whether the given link has a safe HTTP method like GET.

Fragment updates

  • When a selector was not found in the response, the error notification now offers a link to show the unexpected response.
  • The event up:fragment:destroy can no longer be prevented.

History

  • Clicking a link with an [up-restore-scroll] attribute will no longer crash if no previous scroll position for given URL is known (#25)
  • Fix a bug where going back in history would sometimes not call destructors (#24)

Forms

  • up.observe() no longer sends multiple callbacks when a previous callback was slow to respond.

Tooltips

  • Fix a bug where tooltips would sometimes stay open when many tooltips are opened and closed concurrently.

Server protocol

Animation

  • up.motion.none() has been removed without replacement. Just pass false or the string 'none' to indicate a animation or transition which has no visual effects and completes instantly.
  • up.motion.finish() is now async. It returns a promise that fulfills when all animations are finished.
  • up.motion.finish() now also finishes animations in ancestors of the given element.

Modals

  • up.follow() will now open a modal if the given link has an [up-modal] attribute
  • a[up-modal] links can now have an [up-fail-target] attribute to indicate which selector to replace for an non-200 response
  • Fix a bug where preloading an up-modal link would create an invisible .up-modal container in the DOM.

Popups

  • up.follow() will now open a popup if the given link has [up-popup] attribute
  • up-popup links can now have an up-fail-target attribute to indicate which selector to replace for an non-200 response
  • Fix a bug where preloading an up-popup link would create an invisible .up-popup container in the DOM.
  • up.popup.attach() now throws an error if neither { url } nor { html } options are given.

Events

  • When async functions emit an event and that event is prevented, the async function now rejects with an Error.
  • When async functions are called wth { confirm: true } and the user denies confirmation, the async function now rejects with an Error.

Utility functions

  • up.util.setTimer() is now always async, even when called with a delay of 0 (zero). The function is now stable.
  • up.util.isHash() has been removed without replacement. In your code you can replace up.util.isHash(x) with up.util.isObject(x) && !up.util.isFunction(x).
  • up.util.resolvedDeferred() has been removed without replacement. Use Promise.resolve() instead.
  • up.util.resolvedPromise() has been removed without replacement. Use Promise.resolve() instead.
  • up.util.rejectedPromise() has been removed without replacement. Use Promise.reject() instead.
  • up.util.unresolvableDeferred() has been removed without replacement. Use new Promise(function() {}) instead.
  • up.motion.when() has been removed without replacement. Use Promise.all() instead.
  • up.util.isString() now also returns true for String instances (in addition to string literals)
  • up.util.isNumber() now also returns true for Number instances (in addition to number literals)

Ruby on Rails bindings

  • New method up.fail_target available in controllers, helpers and views. It returns the selector targeted for a failed response.
  • New method up.fail_target?(target) available in controllers, helpers and views. It returns whether the given selector is targeted for a failed response.
  • New method up.any_target?(target) available in controllers, helpers and views. It returns whether the given selector is targeted for a either a successful or failed response.

0.37.0

Compatible changes

  • Fix a bug where replacing the <body> element would not trigger destructor functions in the old <body>.
  • Fix a bug where [up-layer] attributes or { layer } options were ignored.
  • a[up-target] and [form[up-target]] get a new modifying attribute [up-fail-layer]. Use it to set the layer to update if the server sends a non-200 status code. Valid values are auto, page, modal and popup.
  • JavaScript functions like up.replace() or up.submit() now have a { failLayer } option.

0.36.2

Compatible changes

0.36.1

Compatible changes

  • npm package now expresses Unpoly's dependency on jquery.
  • Modals no longer close when clicking an element that exists outside the modal's DOM hierarchy.
  • Fix a bug on IE11 where modals would immediately close after opening if the opening link had an [up-instant] attribute and the destination page was already cached.

0.36.0

Compatible changes

0.35.2

Compatible changes

  • unpoly-rails now supports Rails 5

0.35.1

Compatible changes

  • Fix a bug where an Unpoly app would crash when embedded as an <iframe> if the user blocks third-party cookies and site data
  • Fix a bug where the up global wasn't registered on window when using Webpack

0.35.0

Compatible changes

  • Remove a use of global $ that prevented Unpoly from being used with with jQuery.noConflict().
  • Fix a bug where replacing the <body> element would lose the body class and other attributes
  • Fix a bug where Unpoly would set the document title to a <title> tag of an inline SVG image.

Incompatible changes

  • Drop support for IE 9, which hasn't been supported on any platform since January 2016.
  • Drop support for IE 10, which hasn't been supported since January 2016 on any platform except Windows Vista, and Vista is end-of-life in April 2017.

0.34.2

Compatible changes

  • The scroll positions of two viewports with the same selector is now restored correctly when going back in history.
  • Fix a bug where new modals and popups would sometime flash at full opacity before starting their opening animation.

0.34.1

Compatible changes

  • Elements with up-show-for and up-hide-for attributes can now be inserted dynamically after its controlling up-switch field has been compiled.
  • Unpoly no longer strips a trailing slash in the current URL during startup

0.34.0

Compatible changes

Breaking changes

0.33.0

Compatible changes

  • When a fragment updates cannot find the requested element, you can now define a fallback selector to use instead.

    A { fallback } option has been added to all Javascript functions that update fragments, like up.replace().

    Also an [up-fallback] attribute has been added to all CSS selectors that update fragments, like for a[up-target].

    You can also define fallbacks globally using the up.dom.config property.

  • Unpoly no longer crashes when a request fails due to a timeout or network problem. In such cases, async functions (like up.replace()) will leave the page unchanged and reject the returned promise.

  • Functions that make a request (like up.replace() or like up.ajax()) now accept a new option { timeout }.

  • Modals no longer create an .up-modal element when the server returns a non-200 status and the { failTarget } is replaced instead

  • Popups no longer create an .up-popup element when the server returns a non-200 status and the { failTarget } is replaced instead

  • Improve performance when updating fragments without transitions

  • When updating the body element with a transition, that transition is now silently ignored instead of throwing an error.

  • up.util.resolvedPromise() now accepts arguments which will become the resolution values.

  • up.util.resolvedDeferred() now accepts arguments which will become the resolution values.

  • New utility method up.util.rejectedPromise().

  • up.first() has new option { origin }. You can use it provide a second element or selector that can be referenced as & in the first selector:

    $input = $('input.email');
up.first('.field:has(&)', $input); // returns the .field containing $input

  • Fix a bug where the document title wasn't restored when the user uses the back button

  • When revealing a page fragment, Unpoly will include the element's top and bottom margin in the area that should be revealed.

Breaking changes

  • up.replace() now returns a rejected promise if the server returns a non-200 status code.
  • up.util.merge() has been replaced by up.util.assign(), which no longer makes exceptions for null and undefined property values. This behaves like Object.assign.
  • The up.flow module has been renamed to up.dom.
  • The up.navigation module has been renamed to up.feedback.
  • Functions that measure position, dimensions or margin now return floats instead of rounded integers.

0.32.0

Compatible changes

  • Fix a bug where morphing an [up-keep] element with a destructor would throw an error.
  • Fix a bug where an [up-keep] element would lose its jQuery event handlers when it was kept.
  • Fix a bug where up.log.disable() did not persist through page reloads.
  • Fix a bug where up.reveal() would scroll too far if the viewport has a padding-top.
  • Fix a bug where up.reveal() would not scroll to an element at the bottom edge of the visible area if up.layout.config.snap is set.
  • Several features have been promoted from experimental API to stable API:
  • When targeting an URL with a #hash, the viewport will now scroll to the first row of an element with that ID, rather than scrolling as little as possible.

Breaking changes

  • Modals can no longer grow wider than the screen

  • The spacing around a modal dialog is longer implemented as a margin of .up-modal-dialog. It is now a padding of .up-modal-viewport. This makes it easier to set the width or max-width of the dialog box.

    If your project has custom Unpoly styles, you should grep your CSS files for changes to the margin of .up-modal-dialog and set it as a padding on .up-modal-viewport[flavor=default] instead.

0.31.2

Compatible changes

  • Unpoly can now be installed as an npm module called unpoly.

0.31.0

Compatible changes

  • Drawers are now a built-in modal flavor! Use the [up-drawer] attribute to open page fragements in a modal drawer that slides in from the edge of the screen.

Breaking changes

0.30.1

Compatible changes

0.30.0

Breaking changes

  • If you are using Unpoly's Boostrap integration, you now need to include unpoly-bootstrap3.js after you include the Bootstrap CSS.
  • Fix some issues when using Unpoly together with Bootstrap modals.

0.29.0

Compatible changes

  • up.popup.attach() now has a { html } option. This allows you to extract popup contents from a HTML string without making a network request.
  • up.tooltip.attach() now has a { text } option which automatically escapes the given string.
  • Fix a bug on Firefox where the page width would jump by the scrollbar width when opening a modal.
  • Fix a bug where modals would close when following a link to a cached destination.

Breaking changes

  • Events handled by Unpoly selectors will no longer bubble up the DOM.

0.28.1

Compatible changes

  • up.tooltip.attach() now has a { text } option which automatically escapes the given string.
  • Fix a bug where Unpoly would hang when parsing a page with a <head> but without a <title>

0.28.0

Compatible changes

  • The error notification is now easier to read and can be closed.
  • When a target selector was not found in the response, the error notification now offers a link to re-request the response for inspection.
  • Compilers can now return an array of functions that will all be called when the element is destroyed.
  • up.observe() now works on checkboxes and radio buttons.
  • up.observe() can now be called with multiple form fields, or any container that contains form fields.
  • When opening a modal you can now pass an option { closable: false } or set an up-closable='false' attribute This lets you disable the default methods to close a modal (close button, clicking on the backdrop, pressing ESC). You can also configure this globally by setting up.modal.config.closable.
  • Fix a bug where up.observe(form, options) would not respect options.
  • Fix a bug where up.autosubmit(form) was not published.
  • Fix a bug where falling back to non-AJAX page loads on old browsers would not work

Breaking changes

0.27.3

Compatible changes

  • Popups and modals will no longer try to restore a covered document title and URL if they were opened without pushing a history entry.
  • When fragments are replaced without pushing a new history entry, the document title will no longer be changed by default.

Breaking changes

0.27.2

Compatible changes

  • Fix a bug where the back button would not work if the document contained carriage returns (\r).
  • Fix a bug where auto-closed modals and popups would overwrite a changed browser location with their cached "covered URL"

Breaking changes

  • Links with up-target now prefer to update elements within their own layer (page, modal, or popup). Only when the target element doesn't exist within the link's layer, Unpoly will look through all layers from top to bottom.

0.27.1

Compatible changes

  • Fix a bug where absolutely positioned elements would be offset incorrectly during transitions
  • Fix a bug where inserted elements were not revealed within their viewport
  • When validating a form with transitions, transitions are no longer applied

Breaking changes

  • When replacing multiple page fragments at once, only the first fragment is revealed within its viewport

0.27.0

Compatible changes

  • Calling up.log.enable() will now keep logging enabled for the remainder of this browser session (and persist through page reloads).
  • Added experimental events to observe history changes: up:history:push (preventable), up:history:pushed and up:history:restored
  • Fix a bug where prepending or appending multiple elements with :before / :after pseudo-classes would not work correctly in tables.
  • Fix a bug where calling up.animate() with { duration: 0 } would return a promise that never resolved.
  • A click on the page body now closes the popup on mousedown instead of click. This fixes the case where an [up-instant] link removes its parent and thus a click event never bubbles up to the body.
  • When opening a modal, elements behind the dialog can now be moved correctly when scrollbars have custom styles on ::-webkit-scrollbar. To take advantage of this, make sure to also style scrollbars on elements with an [up-viewport] attribute.
  • Fix a bug where up.tooltip.config was not publicly acccessible.
  • Fix a bug where up.tooltip.isOpen() was not publicly acccessible.
  • New tooltip configuration options: config.openDuration, config.closeDuration, config.openEasing, config.closeEasing
  • Opening/closing many tooltips concurrently now behaves deterministically.
  • Opening/closing many popups concurrently now behaves deterministically.
  • Opening/closing many modals concurrently now behaves deterministically.
  • IE9 fixes: Polyfill window.console and several properties (log, debug, info, warn, error, group, groupCollapsed, groupEnd)

Breaking changes

  • Tooltips now open and close much quicker.
  • Popups now open and close much quicker.
  • .up-current now considers two URLs different if they have different query strings.

0.26.2

Compatible changes

  • Popups anchored to fixed elements are now positioned correctly if the document is scrolled
  • Tooltips can now be anchored to fixed elements
  • up-modal and up-popup now support an up-method modifier.

0.26.1

Breaking changes

  • When inserting a page fragment with a <script src="..."> tag, the linked JavaScript is no longer loaded and executed. Inline scripts will still be executed. You can configure this behavior using the new up.flow.config property.

0.26.0

Compatible changes

  • Popups no longer scroll with the document if they are attached to an element with position: fixed
  • Tooltips no longer flicker if an [up-tooltip] elements has children
  • Tooltips no longer flicker if the user moves the mouse too close to the tooltip triangle
  • Before compiling the body, Unpoly now explicitly waits until user-provided compiles have been registered and the DOM is ready.
  • Debugging messages in the developer console are now disabled by default. Call up.log.enable() to get them back.
  • New configuration options in up.log.config: up.log.config.enabled, up.log.config.collapse and up.log.config.prefix.
  • Improve formatting of error messages.
  • New experimental utility function up.util.escapeHtml().
  • If an error is thrown before the document is ready, Unpoly now waits until the document is ready before showing the red error box.

0.25.2

Compatible changes

  • Fix a bug where submitting a form with file uploads would throw an error "Cannot convert FormData into a query string"

0.25.1

Compatible changes

  • Fix a bug where up.ajax() would incorrectly re-use form responses even if the form data differed
  • Fix a bug with the up-observe UJS attribute throwing an error when used
  • Fix a bug where if multiple compilers with destructors are applied to the same element and the element is removed, only the last destructor was called.

0.25.0

Compatible changes

  • New modal default up.modal.config.sticky
  • New experimental function up.modal.flavor() to register modal variants (like drawers).
  • Fix a bug where compilers and macros with higher priorities were executed last (instead of first like it says in the docs).
  • Fix a bug that would occur if two compiled elements, that were nested within each other, would raise an error if the outer element was destroyed and both compilers have destructor functions.
  • Fix a bug where replacing the body tag would raise an error if any element in the old <body> had a destructor function.
  • The promise returned by up.replace() now waits for transitions to complete before resolving
  • Fix a bug where an error would be shown when opening a modal while another modal was still loading
  • Fix a bug where two popups would be shown when opening a popup while another popup was still loading
  • New options for up.popup.config:
    • up.popup.config.openDuration
    • up.popup.config.closeDuration
    • up.popup.config.openEasing
    • up.popup.config.closeEasing
  • Modals now longer addsa right padding to the <body> if the document has no vertical scroll bars
  • Animations now wait until the browser signals completion of the CSS transition. Previously animations were canceled after its duration, which might or might not have matched to the actual last animation frame.

Breaking changes

  • When opening a modal while another modal is open, the first modal will be closed (with animation) before the second modal opens (with animation)
  • When opening a popup while another popup is open, the first popup will be closed (with animation) before the second popup opens (with animation)
  • User-defined macros are now always run before built-in macros. This way you can set a[up-dash] and [up-expand] from your own macros.

0.24.1

Compatible changes

  • Fix a bug that would stop transitions from working.

0.24.0

Compatible changes

  • New function up.modal.extract() to open a modal from an existing HTML string.
  • up.ajax() now also accepts the URL as a first string argument.
  • Expanded links to modals or popups now get a pointer cursor via CSS
  • New options for up.modal.config:
    • up.modal.config.openDuration
    • up.modal.config.closeDuration
    • up.modal.config.openEasing
    • up.modal.config.closeEasing
    • up.modal.config.backdropOpenAnimation
    • up.modal.config.backdropCloseAnimation
    • Also see the breaking changes regarding modal structure below.
  • Calling up.motion.finish() without arguments will now complete all animations and transitions on the screen.
  • Fix a bug where up.motion.finish() would not cancel CSS transitions that were still in progress.
  • Fix a bug where up-active classes where not removed from links when the destination was already preloaded.

Breaking changes

  • Animations when opening or closing a modal now only affect the viewport around the dialog. The backdrop is animated separately. This allows animations like "zoom in", which would look strange if the backdrop would zoom in together with the dialog.

  • The modal's HTML structure has been changed to include a .up-modal-backdrop element:

    <div class="up-modal">
<div class="up-modal-backdrop">
<div class="up-modal-viewport">
  <div class="up-modal-dialog">
    <div class="up-modal-content">
      ...
    </div>
    <div class="up-modal-close" up-close>X</div>
  </div>
</div>
</div>

  • The z-index properties for modal elements have been changed. They might change again in the future.

  • The modal will now take over the document's scrollbars after the open animation has finished. In earlier versions the modal took over as soon as the animation had started.

  • Calling up.motion.finish() with an element will now also complete animations/transitions on children of the given element.

0.23.1

Compatible changes

  • Animations move-to-* and move-from-* now use CSS transforms instead of manipulating the bounding box margins.
  • Fix up.util.trim() not working properly.
  • up.morph() no longer throws an error if called without an options object
  • Custom transitions can now call up.morph() to refer to other transitions
  • Fix a bug where following a link to a preloaded destination would keep the link marked with a up-active class forever.

0.23.0

Compatible changes

  • Unpoly forms can now submit file uploads via AJAX.
  • You can now position tooltips on the left or right side of an element.

Breaking changes

  • Tooltips have a darker background color.
  • The tooltip CSS has been changed to be easier to override.

0.22.1

Compatible changes

  • Fix a bug where the document title wasn't restored when using the back and forward buttons
  • Fix a bug where links would be followed multiple times if the link had an up-dash attribute without a value and also an up-target attribute.
  • Fix a bug where a link would be followed multiple times if the link's click area was expanded using [up-expand] and if the link also had an up-dash attribute.
  • up.destroy() now returns a resolved deferred if the given selector or jQuery collection does not exist

0.22.0

Compatible changes

  • Fix a bug where using the up-confirm attribute would result in an infinite loop
  • Unpoly no longer displays confirmation dialogs when preloading a link that has both up-preload and up-confirm attributes.

Breaking changes

0.21.0

Compatible changes

  • New function up.macro(). This registers a compiler that is run before all other compilers.
  • up.compiler() has a new options { priority }. Compilers with higher priorities are run first.
  • Fix a bug where trying to apply another transition on an element could throw a Maximum call stack exceeded error if the element was already transitioning.

Breaking changes

  • up-toggle has been renamed to up-switch

0.20.0

0.19.0

Compatible changes

  • Elements can now be persisted during page updates using the up-keep attribute.
  • up.proxy.ajax() is now available as up.ajax().
  • up.ajax() can now handle nested objects as { data } option (used to pass form parameters).

Breaking changes

0.18.1

Compatible changes

  • The logging output to the developer console is now much quieter and more useful

0.18.0

Compatible changes

  • New UJS attribute [up-toggle] to show or hide part of a form if certain options are selected or boxes are checked.
  • Links can now have an optional up-confirm attribute. This opens a confirmation dialog with the given message before the link is followed or the modal/popup is opened.
  • New function up.off(). This unregisters an event listener previously bound with up.on().
  • If a container contains more than one link, you can now set the value of the up-expand attribute to a CSS selector to define which link should be expanded.
  • You can now configure a list of safe HTTP methods in up.proxy.config.safeMethods. The proxy cache will only cache safe requests and will clear the entire cache after a unsafe request.
  • Loading modals and popups will now open if there is a fragment update between the modal/popup's request and response.
  • up.follow() and up.replace() now have an option { failTarget }. Use it to define the selector to replace if the server responds with an error.
  • [up-target] and up-follow now have a modifying attribute up-fail-target. Use it to define the selector to replace if the server responds with an error.
  • New utility method up.util.reject()
  • New utility method up.util.only()
  • New utility method up.util.except()
  • Fix a bug where modals could no longer be opened on some browsers
  • When preventing an event emitted by an async function, that function now rejects its promise.
  • Async functions that encounter an error now prefer to reject promises with an Error object (instead of a string with the error message)

Breaking changes

  • By default Unpoly now converts PUT, PATCH and DELETE requests to POST requests that carry their original method in a form parameter named _method. This is to prevent unexpected redirect behavior.

    Web frameworks like Ruby on Rails or Sinatra are aware of the _method parameter and use its value as the method for routing.

    You can configure this behavior in up.proxy.config.wrapMethods and up.proxy.config.wrapMethodParam.

  • The requested selector is now sent to the server as a request header X-Up-Target (this used to be X-Up-Selector). If you are using unpoly-rails, you can access it through up.target (this used to be up.selector).

0.17.0

Compatible changes

Breaking changes

  • When up.observe() is used with a delay of zero, the callback is invoked instantly (instead of being invoked in the next animation frame).

0.16.0

Compatible changes

  • You can now configure up.proxy.config.maxRequests to limit the maximum number of concurrent requests. Additional requests are queued. This currently ignores preloading requests.

    You might find it useful to set this to 1 in full-stack integration tests (e.g. Selenium).

  • Allow to disable animations globally with up.motion.enabled = false. This can be useful in full-stack integration tests like a Selenium test suite.

  • New function up.motion.isEnabled to check if animations will be performed.

  • up.popup.attach() now throws a helpful error when trying to attach a popup to a non-existing element

  • New option up.modal.config.history to configure if modals change the browser URL (defaults to true)

  • New option up.popup.config.history to configure if popup change the browser URL (defaults to false).

  • Fix CSS for popups with a position of "bottom-left".

Breaking changes

  • Popups and modals used to close automatically whenever an element behind the overlay was replaced. This behavior is still in effect, but only if the replacement was triggered by a link or element from within the popup or modal.
  • Popups and modals no longer raise an error if their (hidden) overlay was closed before the response was received.
  • Popups and modals are now compiled before they are animated.

0.15.1

Compatible changes

  • Fix an error where up.form.config was not published. This caused unpoly-bootstrap3.js to throw an error.

0.15.0

Compatible changes

Breaking changes

  • up.observe() now takes the callback function as a last argument. The callback can now longer be passed as a .change option.

0.14.0

Compatible changes

0.13.0

Compatible changes

  • Support for server-side live validation of forms using the [up-validate] selector.
  • Support for non-standard CSS selectors from jQuery, such as :has or :visible.
  • Allow to refer to the current element as & in target selectors. This is useful to reference containers that contain the triggering element, e.g. <a href="/path" up-target=".container:has(&)">
  • Improve automatic generation of selectors for elements when no explicit selector is given.
  • Forms with file inputs will now cause forms to fall back to a standard submission without AJAX. In a future release we will be able to submit file inputs via AJAX.
  • The request cache now reuses responses for body and html when asked for other selectors.
  • Server responses can now change the document title by including an X-Up-Title header.

0.12.5

Compatible changes

  • a[up-target] and up.follow now scroll to a #hash in the link's destination URL
  • When up.replace cannot make a change in old browsers, return an unresolved promise instead of a resolved promise.

0.12.4

Compatible changes

  • When morphing, prevent flickering caused by long repaint frames
  • When morphing don't un-highlight current navigation sections in the element that is being destroyed. This makes for a smoother transition.
  • Fix a bug where compositing wasn't forced properly during an animation

0.12.3

Refactored internals. No API changes.

0.12.2

Compatible changes

  • When marking links as .up-current, also consider the URL behind a current modal or popup to be the "current" URL.

Breaking changes

  • up.bus.emit() is now up.emit()
  • When up.first() finds no match, return undefined instead of null.

0.12.1

Compatible changes

  • up.on() now returns a function that unbinds the events when called
  • Fixed a bug where restoring previous scroll positions was not worked in situations where the same operation would also reveal the replaced element.
  • Various bugfixes

0.12.0

Compatible changes

Breaking changes

  • Remove up.slot, which was poorly implemented, untested, and not much better than the :empty pseudo-selector which has great browser support

  • Replaced the up.bus.on(...) event registry with vanilla DOM events bound to document. Also renamed events in the process.

    Instead of the old ...

    up.bus.on('fragment:ready', function($fragment) {
  ...
};

    ... you now need to write ...

    $(document).on('up:fragment:inserted', function(event) {
  var $fragment = $(this);
  ...
};

    ... or shorter:

    up.on('up:fragment:inserted', function(event, $fragment) {
   ...
};

  • Renamed up.ready() to up.hello(). This will emit an up:event:inserted event for the given element, causing it to be compiled etc.

  • up.popup.open() has been renamed to up.popup.attach().

  • up.modal.open() has been split into two methods up.modal.visit(url) and up.modal.follow($link).

  • up.tooltip.open() has been renamed to up.tooltip.attach().

  • Tooltips now escape HTML by default; To use HTML content, use an [up-tooltip-html] attribute instead.

  • Module configurations are now simple properties like up.layout.config instead of methods like up.layout.defaults(...).

    Instead of the old ...

    up.layout.defaults({ snap: 100 });

    ... you now need to write:

    up.layout.config.snap = 100;

0.11.1

Compatible changes

  • Fix a bug where browsers without CSS animation support would crash after an animation call
  • Expose up.error() as public API. This prints an error message to the error console and throws a new Error with that message.
  • Fix a million bugs related to compatibility with IE9 and IE10

0.11.0

Compatible changes

  • Rework the scrolling implementation so we don't need to scroll elements to the top before replacing them.
  • up.ajax() now only caches responses with a status code of 200 OK
  • When a link with an [up-close] attribute is clicked, the link's default action will only be prevented if the link was actually within a modal or popup.
  • When revealing an element, Up will now compute the correct element position if there are additional positioning contexts between the viewport and the element
  • New option "top" for up.reveal(): Whether to scroll the viewport so that the first element row aligns with the top edge of the viewport. Without this option, up.reveal() scrolls as little as possible.
  • Allow to animate scrolling when the document is the viewport.
  • New up.layout setting fixedRight that contains selectors for elements that are anchored to the right edge of the screen. When opening a modal, these elements will be prevented from jumping around. If you're using unpoly-bootstrap3.js, this will default to ['.navbar-fixed-top', '.navbar-fixed-bottom', '.footer'].
  • Fix a bug in unpoly-rails where the gem would fail to include itself in some versions of Ruby and Rails.

Breaking changes

  • Interactions that would result in an URL change ("pushState") now fall back to a full page load if Unpoly was booted from a non-GET request. More information about the reasons for this.

    This currently works out of the box if you're using Unpoly via the unpoly-rails Rubygem. If you're integrating Unpoly with Bower or manually, you need to have your server app set an _up_request_method cookie with the current request method on every request.

0.10.5

Compatible changes

  • Fix a bug where the proxy would remain busy forever if a response failed.

0.10.4

Compatible changes

  • Fix a bug where hovering multiple times over the same [up-preload] link would not trigger a new request after the cache expired

0.10.3

Compatible changes

  • The default viewport is now document instead of the <body> element.

0.10.2

Breaking changes

  • While following links and submitting forms will still reveal elements by default, direct calls of up.replace() no longer do. This behavior can be activated using the { reveal: true } option.

Compatible changes

0.10.1

Breaking changes

  • up.reveal() now only reveals the first 150 pixels of an element.

0.10.0

Compatible changes

  • Viewport scroll positions are saved when the URL changes and restored when the user hits the back/forward button
  • Allow to link to the previous page using [up-back]
  • Allow to restore previous scroll state using [up-restore-scroll]
  • Instead of saying <tag up-something="true"> you can now simply say <tag up-something>.
  • Create this Changelog.

Breaking changes

  • The option options.scroll and attribute up-scroll have been removed. Instead you can use the boolean option options.reveal or up-reveal to indicate whether an element should be revealed within the viewport before replacement.
  • The string up.history.defaults('popTarget') is now an array of selectors up.history.defaults('popTargets')

0.9.1

Compatible changes

  • Change transition implementation so child elements with collapsing margins don't reposition within the animated element

0.9.0

Compatible changes

  • Elements are now being revealed within their viewport before they are updated
  • Elements that are prepended or appended using :before or :after pseudo-selectors are now scrolled into view after insertion.
  • New option up.layout.defaults('snap') lets you define a number of pixels under which Unpoly will snap to the top edge of the viewport when revealing an element
  • You can now make up.reveal() aware of fixed navigation bars blocking the viewport by setting new options up.layout.defaults('fixedTop') and up.layout.defaults('fixedBottom').

0.8.2

Compatible changes

  • up.reveal() can now reveal content in modals and containers with overflow-y: scroll.
  • Changing the default configuration of an Unpoly module now raises an error if a config key is unknown.
  • Links linking to "#" are now never marked as .up-current.

0.8.1

Compatible chanes

  • You can now include unpoly-bootstrap3.js and unpoly-bootstrap3.css to configure Unpoly to play nice with Bootstrap 3.

Breaking changes

  • Like Bootstrap, the Unpoly modal will now scroll the main document viewport instead of the modal dialog box.

0.8.0

Compatible changes

  • Unpoly will now emit events proxy:busy and proxy:idle whenever it is loading or is done loading content over HTTP.
  • Add an option up.proxy.defaults('busyDelay') to delay the proxy:busy event in order to prevent flickering of loading spinners.

0.7.8

Compatible changes

  • Now longer throws an error if the current location does not match an up-alias wildcard (bugfix).

0.7.7

Compatible changes

  • Allow up-alias to match URLs by prefix (up-alias="prefix*").

0.7.6

Compatible changes

  • Fix what Unpoly considers the current URL of a modal or popup if multiple updates change different parts of the modal or popup.
  • Don't replace elements within a container that matches .up-destroying or .up-ghost (which are cloned elements for animation purposes).

0.7.5

Compatible changes

  • Make sure that an expanded link will be considered a link by adding an up-follow attribute if it doesn't already have an up-target attribute.

0.7.4

Compatible changes

  • Correctly position tooltips when the user has scrolled the main document viewports.
  • Allow popups within modal dialogs.

0.7.3

Compatible changes

0.7.2

Compatible changes

  • When marking links as .up-current, allow to additionally match on a space-separated list of URLs in an up-alias attribute.

0.7.1

Compatible changes

  • Bugfix: Don't consider forms with an up-target attribute to be a link.

0.7.0

Compatible changes

0.6.5

Compatible changes

  • Animation options for up.tooltip.open
  • Consider the left mouse button clicked when event.button is undefined (as happens with `.click()``)

Breaking changes

  • Rename option .origin to .position in up.popup and up.tooltip

0.6.4

Compatible changes

  • Don't follow links while CTRL, Meta or Shift keys are pressed

0.6.3

Compatible changes

  • Show backtraces for Unpoly errors

Breaking changes

  • Rename method up.awaken() to up.compiler()

0.6.2

Compatible changes

  • Option to have a custom HTTP method for up.follow()
  • No longer preloads links with unsafe HTTP methods