@bobfrankston/rmfmail 1.2.2 → 1.2.4

package/client/app.js

@@ -2700,22 +2700,24 @@ window.addEventListener("message", (e) => {
         return;
     }
     if (e.data?.type === "openLink" && e.data.url) {
-        window.open(e.data.url, "_blank", "noopener,noreferrer");
+        const api = window.mailxapi;
+        if (api?.openExternal)
+            api.openExternal(e.data.url);
+        else
+            window.open(e.data.url, "_blank", "noopener,noreferrer");
     }
     if (e.data?.type === "linkClick" && e.data.url) {
         const url = e.data.url;
-        if (window.mailxapi?.platform === "android") {
-            // Android: use mailxapi:// bridge scheme — OnNavigating intercepts it
-            // and opens in system browser. Raw http:// in sub-frames doesn't trigger OnNavigating.
-            const f = document.createElement("iframe");
-            f.style.display = "none";
-            f.src = `mailxapi://openurl?url=${encodeURIComponent(url)}`;
-            document.body.appendChild(f);
-            setTimeout(() => f.remove(), 500);
-        }
-        else {
+        // Route through mailxapi.openExternal — on desktop it spawns the OS
+        // browser via the Node process (window.open stayed LOCAL inside msger's
+        // WebView2 — Bob 2026-06-13 "old bug back"); on Android it uses the
+        // native intent bridge. Falls back to window.open only if the api isn't
+        // present (bare browser / --server mode).
+        const api = window.mailxapi;
+        if (api?.openExternal)
+            api.openExternal(url);
+        else
             window.open(url, "_blank", "noopener,noreferrer");
-        }
     }
     if (e.data?.type === "previewToggleFullscreen") {
         toggleFullscreenPreview();