From 55860369b9d9df29eaacce8cfc08cca86d62a6a4 Mon Sep 17 00:00:00 2001
From: djadji-gueye <sennegueye@gmail.com>
Date: Sat, 8 Aug 2026 15:34:33 +0000
Subject: [PATCH] fix(web): don't reset memory viewer to first asset on delete

---
 .../[[photos=photos]]/[[assetId=id]]/MemoryViewer.svelte      | 4 ----
 1 file changed, 4 deletions(-)

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 64664808d7..3fbf3d1682 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
@@ -185,9 +185,6 @@
     if (!current) {
       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);
@@ -195,7 +192,6 @@
     if (nextTarget) {
       await handleNavigate(nextTarget);
     } else {
-      // No assets left to navigate to (memory was fully emptied and removed).
       init(page);
     }
   };