@bobfrankston/rmfmail 1.1.79 → 1.1.80

package/.commitmsg

@@ -1,14 +1,12 @@
-Fix user-dictionary persistence; correct contacts.md
+Fix: opening an attachment did nothing on desktop
 
-User dictionary never reached the server: mailxapi.js (the desktop IPC
-bridge) had no getUserDict/addUserDictWord methods, so api-client's
-optional-chained calls silently no-op'd — added words lived only in
-localStorage. Added the four bridge methods, a bulk addUserDictWords
-RPC, and a load-time reconcile in spellcheck.ts that pushes any
-localStorage-only words up to userdict.csv so accumulated words are
-recovered.
+Clicking an attachment chip fired a programmatic <a download> click,
+which msger's WebView2 silently drops — so nothing happened and the
+failure was swallowed by a console-only catch.
 
-contacts.md: removed the stale `discovered` documentation — since Q150
-the discovered set is a per-device local cache and is not written to or
-synced via contacts.jsonc. Documented the cloud file as preferred +
-denylist + groups (+ preserved hand-added keys).
+New service method openAttachment saves the attachment to
+~/.rmfmail/attachments/ and opens it with the OS default app (start /
+open / xdg-open), the same in-process pattern as openInWord. The viewer
+now calls it on desktop, keeps the native-bridge path for Android, and
+falls back to the blob download only for a real browser / --server
+mode. Failures now surface via an alert instead of vanishing.

package/client/android-bootstrap.bundle.js

@@ -6253,6 +6253,11 @@ ${bodyEncoded}`;
   async getAttachment(_accountId, _uid, _attachmentId, _folderId) {
     return this.notImpl("getAttachment");
   }
+  // Android opens attachments via the native bridge (_nativeBridge.openAttachment),
+  // not this service path — getAttachment + base64 hand-off covers it.
+  async openAttachment(_accountId, _uid, _attachmentId, _folderId) {
+    return this.notImpl("openAttachment");
+  }
   // Spam / abuse
   async markAsSpamMessages(_accountId, _uids) {
     return this.notImpl("markAsSpamMessages");