@bobfrankston/rmfmail 1.2.185 → 1.2.187

package/client/app.js

@@ -2994,6 +2994,19 @@ window.addEventListener("message", (e) => {
         else
             window.open(url, "_blank", "noopener,noreferrer");
     }
+    if (e.data?.type === "imgLoadFail") {
+        // Remote images failed to load inside the preview iframe even though
+        // remote content was allowed — silent before; now in the daemon log
+        // with the first failing URL (Bob 2026-07-28: Nextdoor digest showed
+        // every image broken while curl fetched them fine).
+        try {
+            logClientEvent("[viewer] remote images failed to load", {
+                failed: e.data.count, total: e.data.total, first: e.data.first,
+            });
+        }
+        catch { /* diagnostic only */ }
+        return;
+    }
     if (e.data?.type === "previewToggleFullscreen") {
         toggleFullscreenPreview();
         return;
@@ -4136,8 +4149,10 @@ document.getElementById("message-viewer")?.addEventListener("dblclick", (e) => {
     // address or subject is a universal text-select gesture; hijacking it for
     // fullscreen collapsed the whole UI to a near-empty viewer and looked
     // broken (Bob 2026-06-05: "double-clicked a from address by mistake and
-    // got this screen"). Fullscreen is still reachable by double-clicking the
-    // message BODY — the iframe posts `previewToggleFullscreen` (app.ts:2411).
+    // got this screen"). The iframe-level dblclick toggle was ALSO removed
+    // (it hijacked word-selection), so this chrome handler is now the only
+    // entry into fullscreen-preview. toggleFullscreenPreview() itself guards
+    // against entering with no message loaded.
     if (target?.closest(".mv-header"))
         return;
     toggleFullscreenPreview();