@bobfrankston/rmfmail 1.0.620 → 1.0.627

package/TODO.md

@@ -787,6 +787,11 @@ Was part of S1 "local-first reconciliation refactor" until 2026-04-23 when S1's
 
 | Item | Version |
 |---|---|
+| **WebView timing forwarded to daemon log + cleanups** — Daemon log shows boot is **~204 ms to showService** (2026-05-09 14:23 run). The "long startup" delay is entirely WebView2 init + JS module cascade + first paint after the daemon hands off. The `[wv N ms]` / `[preview N ms]` / `[search N ms]` marks were `console.log`-only — invisible to the daemon log. Now forwarded via `mailxapi.logClientEvent` so they land alongside `[boot N ms]` for full timeline. Plus: `android.html` removed (renamed `.deleted`); `silent=true` on logit URLs (Android + WebView error handlers) so verbose marks don't spam jserv UI; build clean. Run mailx, check the log — actual breakdown of where the time goes is now visible. | v1.0.626 |
+| **Preview-path timing checkpoints** — User report 2026-05-09: "still seeing very long delays on previews that should be instantaneous? It finally displayed but why?" The boot timing answers cold-start; this answers click-to-preview. New `[preview N ms] showMessage entry / parsedCache HIT|MISS / IPC done (cached, N bytes html) / iframe srcdoc set / iframe load (rendered)` marks. Slow paths now have stage-by-stage breakdown — IPC vs parser vs iframe-paint becomes visible without speculation. | v1.0.625 |
+| **Search history dropdown (recent queries)** — User request 2026-05-09: "the search bar should be a dropdown offering me recent searches so I don't need to type them again. Just recent dropdowns is fine for now without editing and remove from history. Editing is implicit in bringing up a search and being able to edit it." Native HTML5 `<datalist id="search-history">` bound to `#search-input` via `list=` attribute — browser picker handles dropdown UX with no custom code. Backed by localStorage `mailx-search-history` (cap 25, move-to-front dedup). Recorded only when `doSearch(immediate=true)` fires (Enter / scope change) so debounced keystrokes don't pollute the list. Picking a past entry brings it into the input where the user can edit and re-Enter — the edited version becomes the new top entry. | v1.0.624 |
+| **List/search/startup polish + measurement** — User stack 2026-05-09: (a) "long startup — would be nice to see a countup time in addition to the spinner." Live elapsed-seconds counter (ticks 100 ms) appended to `#startup-status`; auto-stops when overlay is removed. (b) "deleted entries reappeared after switching windows." `removeMessagesAndReconcile` now `listCache.clear()`s — pre-fix the per-folder snapshot cache repainted the deleted rows on next visit. (c) "switched to All Inboxes but search is still showing — being ignored?" Both folder handlers (regular + unified) now call `clearSearchMode()` AND clear the input — previously only the input was cleared, leaving `searchMode = true` so subsequent loads were rerouted. (d) "search is suddenly slow." Added `[search N ms] start / IPC begin / IPC done (n/total)` console marks so the actual cost is visible. Pair with `[boot N ms]` and `[wv N ms]` for a full timing picture. | v1.0.623 |
+| **PWA convergence: one HTML, runtime bootstrap detect, MAUI points at index.html** — User insight 2026-05-09: "If I run on a Pixel tablet it should look like the desktop... You're missing the entire point of the PWA approach!" Two HTML files (`index.html` desktop, `android.html` MAUI) had been forking — different toolbars, different button labels, different search controls, different reset wording. CSS responsive layout already drives wide-vs-narrow; the HTML fork was forcing phone-style on tablets regardless of viewport. Convergence: `index.html` now carries the union of platform-runtime concerns (Android import map for in-WebView module resolution, logit error handlers, single boot router that branches on `!window.mailxapi` — present on desktop because msger pre-injects via initScript, absent on Android until `initAndroid()` runs). MAUI's `MainPage.xaml.cs` flipped `webView.Source` to `client/index.html`. `android.html` left in place as a safety net for now; delete after a successful tablet/phone smoke test. Pixel tablet → desktop layout (CSS wide breakpoint). Phone → narrow layout. Browser → desktop layout. Same code path. Plus per-stage boot timestamps `[wv N ms]` from html-parse-start through first rAF, paired with the daemon's `[boot N ms]` lines from v1.0.611 — actual measurement, not theorizing. | v1.0.621 |
 | **Header encoded-words: uniform decode at the storage seam** — User reports 2026-05-09: ".eml file with strange header" (chase / spam .eml had `From: "=?UTF-8?B?...?=" <s@x>` — encoded-word inside quoted-string, RFC-strictly forbidden but common in the wild). Bob: "you aren't parsing encoded header fields correctly. It's not subject that is encoded. You should uniformly process header escapes early in the parsing." Right answer: not per-callsite patches. Added `decodeHeaderWords` helper at the top of `mailx-store/db.ts` using `libmime.decodeWords`; called once in `upsertMessage` for `subject`, `from.name`, `to[].name`, `cc[].name`. Every storage path (IMAP fetch, Gmail API, manual append, eml replay) now decodes uniformly. Safe on already-decoded text — no `=?` markers → no-op. Old rows in DB keep their bad names until re-fetched; new fetches and any sync action that re-upserts the row pick up the fix. | v1.0.618 |
 | **List selection: clicks during in-flight IPC no longer bounce** — User report 2026-05-09: "I just selected the 10:03 message and it showed and then bounced back to the 15:49. I have to be quick to capture the 10:03 before it bounces away." Root cause: `loadUnifiedInbox` and `loadMessages` captured `savedUid` at function start, then awaited the IPC. If you clicked a different row during the await, the new selection painted briefly, then `renderMessages` (post-IPC) cleared it and `restoreSelection` restored the *captured* old uid — your click was overwritten. Fix: read the selected uid LIVE — once before each `restoreSelection` call (just before `renderMessages` clears the DOM). The user's mid-flight click survives the re-render. | v1.0.617 |
 | **Allowlist click: refresh in-memory cache after unblock** — User report 2026-05-09: "I pressed unblock but again it failed. With chase the next run found it unblocked. You added it to allowed but don't know it!" Persistence WAS working — next launch saw the chase.com domain in allowlist. The current-session re-render path was broken: `loadRemote` swapped the iframe but never updated `currentMessage` or the WebView-side `parsedCache` (added this morning for second-view speed). Any subsequent showMessage call hit the stale blocked-version cache and re-rendered the banner. Now `loadRemote` writes the unblocked message into both `currentMessage` and `parsedCachePut(accountId, uid, full)` so future renders agree with what the user just saw. | v1.0.616 |

package/client/app.js

@@ -39,6 +39,7 @@ function propagateAppName() {
     }
 }
 propagateAppName();
+window.__btick && window.__btick("app.ts module body executing");
 let baseTitle = APP_NAME;
 let lastSeenCount = 0;
 let badgeCount = 0;
@@ -336,8 +337,11 @@ initFolderTree(folderTree, (accountId, folderId, folderName, specialUse) => {
     currentFolderSpecialUse = specialUse;
     currentAccountId = accountId;
     currentFolderId = folderId;
+    // Drop search state on folder switch — input alone wasn't enough,
+    // searchMode stayed true and the next loadMessages was rerouted.
     if (searchInput)
         searchInput.value = "";
+    clearSearchMode();
     markAsSeen();
     releaseFocus();
     loadMessages(accountId, folderId, 1, specialUse);
@@ -347,6 +351,14 @@ initFolderTree(folderTree, (accountId, folderId, folderName, specialUse) => {
 }, () => {
     // Unified inbox handler
     currentFolderSpecialUse = "inbox";
+    // Clear search state — switching folders should drop any active filter.
+    // Pre-fix: the search input retained its old value AND search mode
+    // stayed active, so "All Inboxes" appeared to be ignoring its own
+    // contents (Bob 2026-05-09: "I just switched to all inboxes but the
+    // search is still showing even though all the entries are there.").
+    if (searchInput)
+        searchInput.value = "";
+    clearSearchMode();
     releaseFocus();
     loadUnifiedInbox();
     setTitle(`${APP_NAME} - All Inboxes`);
@@ -371,6 +383,8 @@ initMessageList((_accountId, _uid, _folderId) => {
     }
 });
 initViewer();
+window.__btick && window.__btick("init* done — first interactive moment");
+requestAnimationFrame(() => window.__btick && window.__btick("first rAF after init"));
 // Status bar: show focused message UID/folder for debugging. The list
 // fires mailx-focus-changed with the focused envelope (or null). Pure
 // observation — this listener never drives the viewer.
@@ -1476,6 +1490,48 @@ document.addEventListener("mailx-share-intent", ((e) => {
 let searchTimeout;
 const searchInput = document.getElementById("search-input");
 const searchScope = document.getElementById("search-scope");
+// Recent-searches dropdown — backed by localStorage, populated into the
+// existing <datalist id="search-history"> so the browser's native picker
+// shows on focus/click. No edit / delete UI; editing is implicit (pick a
+// past query, modify, hit Enter — the modified version is recorded).
+// Cap at 25 to keep the list usable.
+const SEARCH_HISTORY_KEY = "mailx-search-history";
+const SEARCH_HISTORY_MAX = 25;
+function loadSearchHistory() {
+    try {
+        return JSON.parse(localStorage.getItem(SEARCH_HISTORY_KEY) || "[]");
+    }
+    catch {
+        return [];
+    }
+}
+function saveSearchHistory(list) {
+    try {
+        localStorage.setItem(SEARCH_HISTORY_KEY, JSON.stringify(list));
+    }
+    catch { /* private mode */ }
+}
+function refreshSearchHistoryDatalist() {
+    const dl = document.getElementById("search-history");
+    if (!dl)
+        return;
+    const items = loadSearchHistory();
+    dl.innerHTML = items.map(q => `<option value="${q.replace(/"/g, "&quot;")}"></option>`).join("");
+}
+function recordSearchHistory(query) {
+    const trimmed = query.trim();
+    if (!trimmed)
+        return;
+    const cur = loadSearchHistory();
+    // Move-to-front dedup: if already there, pull it; then prepend.
+    const filtered = cur.filter(q => q !== trimmed);
+    filtered.unshift(trimmed);
+    if (filtered.length > SEARCH_HISTORY_MAX)
+        filtered.length = SEARCH_HISTORY_MAX;
+    saveSearchHistory(filtered);
+    refreshSearchHistoryDatalist();
+}
+refreshSearchHistoryDatalist();
 function doSearch(immediate = false) {
     const query = searchInput.value.trim();
     if (query.length === 0) {
@@ -1507,6 +1563,10 @@ function doSearch(immediate = false) {
     }
     loadSearchResults(query, effectiveScope, currentAccountId, currentFolderId, includeTrash);
     setTitle(`${APP_NAME} - Search: ${query}`);
+    // Only record on `immediate=true` (Enter / scope change) — debounced
+    // typing would otherwise add every keystroke as its own entry.
+    if (immediate)
+        recordSearchHistory(query);
 }
 // Track current folder for scoped search
 let currentAccountId = "";