@bobfrankston/mailx 1.0.445 → 1.0.447

package/client/components/message-list.js

@@ -140,10 +140,25 @@ if (!window.__mailxMultiSelectWired) {
         if (!body?.classList.contains("multi-select-on"))
             return;
         const target = e.target;
-        // A tap on a row is handled by the row's own click listener; only
-        // exit when the tap is on neutral ground (outside the list entirely).
-        if (!target.closest(".ml-row"))
-            exitMultiSelect();
+        // A tap on a row is handled by the row's own click listener.
+        // The toolbar must also be exempt: its trash / spam / etc.
+        // buttons operate ON the current multi-selection, so a tap on
+        // them should NOT clear selection before the button's click
+        // handler runs (otherwise getSelectedMessages returns empty
+        // and the action no-ops — Android-reported 2026-04-30: "press
+        // multiple circles, press trashcan, checks vanish, nothing
+        // deleted"). Same logic for the folder-tree (drop targets,
+        // future: bulk move). Exit only on a tap to genuine neutral
+        // ground.
+        // Exempt: rows (handled by their own listener), toolbar buttons
+        // (delete/spam/etc. operate ON the selection — clearing it here
+        // empties the selection before the click runs), folder-tree
+        // (drop targets / future bulk move), and the context menu
+        // (right-click → "mark read" / "move to" / etc. all need the
+        // selection intact when the menu item runs).
+        if (target.closest(".ml-row, .toolbar, .folder-tree, .ctx-menu, #btn-tb-delete, #btn-tb-spam"))
+            return;
+        exitMultiSelect();
     }, true);
 }
 function selectRange(from, to) {
@@ -549,6 +564,15 @@ function renderMessages(body, accountId, items) {
     body.replaceChildren(fragment);
 }
 function selectFirst(body) {
+    // Narrow viewports (Android, phone-sized): don't auto-select. The
+    // click handler in app.ts switches the layout to "narrow-active" on
+    // any list-row click, which on a phone means the message viewer takes
+    // over the screen and hides the list. Auto-selecting at startup
+    // therefore lands the user in the LAST letter they read instead of
+    // the inbox summary they wanted. Desktop unchanged — auto-select
+    // remains useful when the list and viewer are side-by-side.
+    if (window.innerWidth <= 768)
+        return;
     const firstRow = body.querySelector(".ml-row");
     if (firstRow)
         firstRow.click();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/mailx",
-  "version": "1.0.445",
+  "version": "1.0.447",
   "description": "Local-first email client with IMAP sync and standalone native app",
   "type": "module",
   "main": "bin/mailx.js",

package/packages/mailx-store-web/android-bootstrap.js

@@ -1067,11 +1067,17 @@ export async function initAndroid() {
         }
         syncManager.syncAll().catch(e => console.error(`[android] Periodic sync error: ${e.message}`));
     }, SYNC_INTERVAL_MS);
-    // Immediate sync when app comes back to foreground (e.g. user switches from
-    // another app). Without this, new messages wait up to 2 minutes after resume.
+    // Immediate sync + send-queue drain when app comes back to foreground
+    // (e.g. user switches from another app). Without the send-queue drain,
+    // a message queued while offline waits up to 2 minutes after resume
+    // before retrying — long enough for the user to think it's stuck.
     document.addEventListener("visibilitychange", () => {
         if (document.visibilityState === "visible") {
             console.log("[sync] resume poll");
+            for (const account of db.getAccounts()) {
+                syncManager.processSendQueue(account.id)
+                    .catch(e => console.error(`[android] resume send-drain ${account.id}: ${e.message}`));
+            }
             syncManager.syncAll().catch(e => console.error(`[android] Resume sync error: ${e.message}`));
         }
     });

package/rebuild.cmd

@@ -1,12 +1,12 @@
 @echo off
-REM ─────────────────────────────────────────────────────────────────────────
+REM -------------------------------------------------------------------------
 REM  rebuild.cmd — one-shot release: npmglobalize + APK.
 REM  Runs the desktop release workflow (npmglobalize commits, tags, bumps,
 REM  publishes the npm package) and, only if that succeeds, rebuilds the
 REM  Android MAUI APK + copies it into download/apks/ + updates versions.json.
 REM  Anything non-zero from npmglobalize aborts before the APK stage — no
 REM  point building an APK against a failed publish.
-REM ─────────────────────────────────────────────────────────────────────────
+REM -------------------------------------------------------------------------
 
 cls
 setlocal

package/#build-apk.cmd.asv#

@@ -1,4 +0,0 @@
-setlocal
-cd %~dp0android-maui
-call build-apk.cmd
-cls &