From 3dda811bf6d136a627ec64ce19fe0a7689c42c75 Mon Sep 17 00:00:00 2001 From: djadji-gueye Date: Sat, 8 Aug 2026 15:31:53 +0000 Subject: [PATCH] fix(web): don't reset memory viewer to first asset on delete --- .../[[assetId=id]]/MemoryViewer.svelte | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/web/src/routes/(user)/memory/[[photos=photos]]/[[assetId=id]]/MemoryViewer.svelte b/web/src/routes/(user)/memory/[[photos=photos]]/[[assetId=id]]/MemoryViewer.svelte index df484fba81..64664808d7 100644 --- a/web/src/routes/(user)/memory/[[photos=photos]]/[[assetId=id]]/MemoryViewer.svelte +++ b/web/src/routes/(user)/memory/[[photos=photos]]/[[assetId=id]]/MemoryViewer.svelte @@ -186,8 +186,18 @@ return; } + // Capture where to land next *before* deleting, since the asset being + // removed will no longer resolve via getMemoryAsset() afterwards. + const nextTarget = current.next?.asset ?? current.previous?.asset; + await memoryManager.deleteAssetFromMemory(current.asset.id); - init(page); + + if (nextTarget) { + await handleNavigate(nextTarget); + } else { + // No assets left to navigate to (memory was fully emptied and removed). + init(page); + } }; const handleDeleteMemory = async () => {