The XHR error handling was duplicated, as we already handle this in
`core/src/init.js` where we intercept Fetch API and XHR API.
So we can drop this jQuery specific duplicate.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
After ec9e283e there was still such a problem with the legacy app navigation
snapper that its width was only 266 px on the RTL layout instead of the
normal 300 px. The 266 px is the default width of Snap.js module. While the
left side snapper width is configured with the property maxPosition, the right
side snapper is configured by passing a negative value for the property
minPosition.
Signed-off-by: Pauli Järvinen <pauli.jarvinen@gmail.com>
Moment doesn't have aliases for every locale and doesn't parse some locale IDs correctly so we need to alias them
Close#27982
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
Snap.js is not robust enough to prevent multiple calls to open() or
close(), so we added more checks to prevent these happening even when an
animation is in progress.
Because if we let this through, snap.js will not notice that the
animation is already done (or a duplicate animation was started),
so the "transitionend" event will not fire a second time.
During an animation, snap.js sets up a setInterval() that hogs the CPU
during the animation. Since a transition doesn't always end due to the
above conditions, that CPU hogging would stay forever.
This is the best workaround so far, it seems it's not possible to cancel
that interval from the outside nor to trigger events to make it do so.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
