Version 3.7.0 Show archive.org snapshot broke some things in complex forms. Sorry for that. Concurrent user input is hard.

3.7.1

This change fixes two regressions for form field watchers, introduced by 3.7.0 Show archive.org snapshot :

When a change is detected while waiting for an async callback, prevent the new callback from crashing with Cannot destructure property { disable } of null.
When a change is detected while waiting for an async callback, the full debounce delay of that new change is honored.

3.7.2

This change addresses multiple edge cases with concurrent user input during form validations Show archive.org snapshot :

It is now possible to queue a validation for a fragment while a validation request for the same target is still loading.
Validations no longer throw an error if a targeted fragment is destroyed while a validation request is loading. Instead Unpoly will only update the fragments that are still present on the page (if any).
Validations are now aborted if the entire <form> element is aborted Show archive.org snapshot . Previously individual validations were aborted when their target was aborted.
up.validate() Show archive.org snapshot now rejects with an up.Aborted error if a debounce delay was aborted (by aborting the <form> element).
When a new validation is queued while a previous validation request is still loading, the full debounce delay of the new validation is now honored.

When the user changes a form field while a previous autosubmission is still loading, prevent that new change from being lost.
A debounce delay is now aborted if the entire <form> element is aborted. It no longer aborts the delay when the form's target is aborted.

Optional target selectors Show archive.org snapshot (with :maybe Show archive.org snapshot suffix) are now included in the X-Up-Target Show archive.org snapshot header if they match in the current page. Previously optional selector parts were always omitted from X-Up-Target Show archive.org snapshot .
The event up:fragment:aborted Show archive.org snapshot now has a new { reason } property. Its a value is a string describing the reason for the fragment being aborted.

Fix a bug where, when rendering multiple fragments from a cached Show archive.org snapshot response, the new fragments would not be revalidated Show archive.org snapshot .
This also affected render passes with [up-hungry] Show archive.org snapshot fragments.
Targeting sibling elements Show archive.org snapshot now supports union selectors like .parent .foo, .parent .bar.