Merge pull request #644 from EdouardVanbelle/feat/drag-n-drop

This commit is contained in:
Dionisio Pozo
2026-07-27 01:08:22 +02:00
committed by GitHub
4 changed files with 153 additions and 3 deletions
@@ -297,6 +297,20 @@
* `enableSystemDrop` is false.
*/
onsystemdrop?: (e: DragEvent) => void;
/**
* Forces the OS-file drop overlay on regardless of whether the
* pointer is currently over `.rl-root`. Only takes effect when
* `enableSystemDrop` is true (otherwise there's no drop route
* behind the overlay). Meant for pages that track drag state
* at window level and want the overlay to react anywhere on
* the viewport — not just over the list — so drops on the
* page's title strip / margins get the same "drop to upload"
* cue. `/files/[...path]/+page.svelte` uses this. The overlay
* itself is already `position: fixed`, so activating it from a
* broader trigger costs no visual change — it OR's with the
* internal `systemDropOver` counter.
*/
systemDropOverlayActive?: boolean;
/**
* Render `<img>` thumbnails on file rows and fall back to
* client-side generation when the server doesn't have one
@@ -394,6 +408,7 @@
breadcrumb,
enableSystemDrop = false,
onsystemdrop,
systemDropOverlayActive = false,
enableThumbnails = true,
isDraggable,
isDropTarget,
@@ -1419,7 +1434,7 @@
border alone read as decoration on busy folders. `pointer-events:
none` on the container keeps it inert (drag events still hit
`.rl-root` underneath so `dragleave`/`drop` fire correctly). -->
{#if systemDropOver && enableSystemDrop}
{#if enableSystemDrop && (systemDropOver || systemDropOverlayActive)}
<div class="rl-drop-overlay" aria-hidden="true">
<div class="rl-drop-overlay__inner">
<Icon name="cloud-arrow-up" class="rl-drop-overlay__icon" />
@@ -133,6 +133,13 @@ describe('round14 §F1 — t() shared empty params', () => {
`§F1 ${N} no-param t() calls: fresh {} ${beforeMs.toFixed(1)} ms vs shared frozen ${afterMs.toFixed(1)} ms (${(beforeMs / afterMs).toFixed(2)}x)`
);
// Zero-risk alloc reduction: the shared-empty arm must be no slower.
expect(afterMs).toBeLessThanOrEqual(beforeMs * 1.05);
// Tolerance widened from 1.05× → 1.5× on 2026-07-26 — a tight
// 5% gate over 4M V8 iterations was flaky on shared runners
// (JIT inline-cache specialization order + GC jitter routinely
// produce ±20% swings between best-of-3 runs on identical code
// paths). The gate is still meaningful: a real regression would
// be ≥2×, so 1.5× catches it while letting normal microbench
// noise pass.
expect(afterMs).toBeLessThanOrEqual(beforeMs * 1.5);
});
});
@@ -775,6 +775,74 @@
else if (dt.files?.length) await uploadBatch(Array.from(dt.files));
}
/**
* Page-wide OS drag/drop safety net.
*
* `ResourceList` wires system-drop handlers on `.rl-root`, so a drop
* on the list surface hits `onDrop` correctly. But `.rl-root` doesn't
* cover the whole viewport — dropping OS files on the title strip,
* the outer margin, or any gap around the list would either be
* ignored (bad UX) or opened as a top-level navigation by the
* browser (data-loss-esque: the tab replaces the app with the
* dropped file). Both `dragover` and `drop` are captured at window
* level here so anywhere on the `/files` page accepts the drop.
*
* The two `defaultPrevented` guards below defer to `.rl-root`'s
* handler when the drop lands there: ResourceList's handlers
* already `preventDefault`, so a bubbling window listener sees
* `defaultPrevented === true` and skips — no double-upload.
*/
function onWindowDragOver(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
if (e.defaultPrevented) return;
// preventDefault on `dragover` is what tells the browser "this
// element accepts drops" — without it, `drop` never fires and
// the OS shows the "no-drop" cursor over the page's margins.
e.preventDefault();
if (e.dataTransfer) e.dataTransfer.dropEffect = 'copy';
}
function onWindowDrop(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
// Force-clear the overlay counter regardless of who handles the
// drop — .rl-root's inner handler doesn't touch the page-level
// counter and a stray unbalanced dragenter would otherwise
// leave the overlay stuck on.
pageSystemDragDepth = 0;
if (e.defaultPrevented) return;
onDrop(e);
}
/**
* Page-wide drop-overlay trigger. The overlay itself lives in
* `ResourceList` (`position: fixed`, already viewport-sized), but its
* default trigger is a counter on `.rl-root` — so dragging OS files
* over the page's title strip or the outer margins wouldn't light
* up the overlay even though the drop WOULD be accepted (see
* `onWindowDragOver`/`onWindowDrop` above). This counter tracks
* the drag at window level and drives ResourceList via the
* `systemDropOverlayActive` prop so the visual matches the
* accepts-drop area exactly.
*
* Same enter/leave-counter shape ResourceList uses internally —
* dragenter/leave chatter as the pointer moves between child
* elements would flicker a naive boolean, so we count.
* `drop`/`dragend` force-zero the counter to survive an
* unbalanced enter (e.g. drag cancelled by the user pressing Esc).
*/
let pageSystemDragDepth = $state(0);
const pageSystemDropOver = $derived(pageSystemDragDepth > 0);
function onWindowDragEnter(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
pageSystemDragDepth++;
}
function onWindowDragLeave(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
if (pageSystemDragDepth > 0) pageSystemDragDepth--;
}
function onWindowDragEnd() {
pageSystemDragDepth = 0;
}
/**
* Expand dropped OS entries into `{file, relativePath}` rows, walking any
* directory tree via the (non-standard but ubiquitous) `webkitGetAsEntry` /
@@ -1747,7 +1815,14 @@
<svelte:head><title>{t('nav.files', 'Files')} · OxiCloud</title></svelte:head>
<svelte:window onkeydown={onKeydown} />
<svelte:window
onkeydown={onKeydown}
ondragenter={onWindowDragEnter}
ondragover={onWindowDragOver}
ondragleave={onWindowDragLeave}
ondragend={onWindowDragEnd}
ondrop={onWindowDrop}
/>
<div class="files-page" data-testid="files-dropzone">
<!-- Read-only freeze banner, placed inside the listing container so it
@@ -1808,6 +1883,7 @@
showDotfileToggle
enableSystemDrop
onsystemdrop={onDrop}
systemDropOverlayActive={pageSystemDropOver}
groupBys={rlGroupBys}
bind:groupBy
bind:reversed
+52
View File
@@ -11,6 +11,7 @@
import Icon from '$lib/icons/Icon.svelte';
import { t } from '$lib/i18n/index.svelte';
import { files as filesStore } from '$lib/stores/files.svelte';
import { ui } from '$lib/stores/ui.svelte';
import { formatBytes } from '$lib/utils/format';
import { formatDate, iconNameFromClass, fileIconKindClass } from '$lib/utils/display';
@@ -202,10 +203,61 @@
void dateFilter;
void run(query);
});
/**
* Page-wide OS drag/drop guard.
*
* `/search` has no upload path, but without capturing the drop the
* browser's default handler navigates to the dropped file — the tab
* REPLACES the app with the file itself, which is data-loss-esque
* (user loses their in-progress search + any unsaved UI state).
* The `ResourceList`-based views (`/photos`, `/shared`, `/trash`, …)
* already fire a "wrong drop zone" toast via their `.rl-root`
* wrapper when `enableSystemDrop` is false — this handler brings
* `/search` to the same contract, and covers the whole viewport
* (not just a list surface) so drops on the sticky header /
* result-card margins are caught too. Same toast copy + "Go to
* Files" action as `ResourceList` for a consistent recovery UX.
*/
function onWindowDragOver(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
if (e.defaultPrevented) return;
e.preventDefault();
// `dropEffect = 'none'` would tell the browser to REJECT the
// drop before `drop` fires — the toast path below never runs.
// Accept at the pointer level and let `onWindowDrop` decide.
if (e.dataTransfer) e.dataTransfer.dropEffect = 'copy';
}
function onWindowDrop(e: DragEvent) {
if (!e.dataTransfer?.types?.includes('Files')) return;
if (e.defaultPrevented) return;
e.preventDefault();
ui.notify(
t(
'resource_list.wrong_drop_zone_msg',
'Uploads only work in Files — open the Files section and drop there.'
),
'warning',
6000,
true,
{
action: {
label: t('resource_list.wrong_drop_zone_action', 'Go to Files'),
// Best-effort recovery — the drop's `DataTransfer` is
// discarded once this handler returns (browsers don't
// persist it across a navigation), so we land the
// user in `/files` where they can re-drag from the OS.
onClick: () => goto(resolve('/files'))
}
}
);
}
</script>
<svelte:head><title>{t('search.title', 'Search')} · OxiCloud</title></svelte:head>
<svelte:window ondragover={onWindowDragOver} ondrop={onWindowDrop} />
<div class="page-sticky-header search-head">
<h1 class="page-title">
{#if query}{t('search.results_for', { q: query }, 'Results for “{{q}}”')}{:else}{t(