[QA] §K Features end-to-end: Remind Me Later, advanced search filters, notification content + click target #180

New Issue

2026-09-17T23:24:08-04:00

jared commented

2026-09-17 23:24:08 -04:00

Migrated from LOTUS_TESTING.md §K on 2026-09-17 — the file is now reference-only.

How to report: tick each item as it passes; on FAIL comment with what you saw vs expected, browser/OS, web (chat.lotusguild.org) vs desktop (Tauri), theme, and any browser-console errors. Screenshots for anything visual.

Checklist

K1. Remind Me Later
K2. Advanced search filters (P4-9)
K3. Notification content + click target (P5-20 partial)

K1. Remind Me Later

On a message, ··· → Remind Me, pick a short preset (the 20-min one, or wait one out).
Expected: when due, a Lotus toast fires linking to that message; the reminder then clears itself. Survives a reload while pending (stored in account data).

K2. Advanced search filters (P4-9)

In message search: use the sender picker (instead of typing from:@user), the date-range quick presets (Today / Last week / Last month / Last year), and the Has link toggle.
Expected: each narrows results correctly and reflects in the search.

K3. Notification content + click target (P5-20 partial)

Trigger a desktop/browser notification for a new message.
Expected: it shows the real message body (username: message, not "New inbox notification from…"); clicking it brings the window to front and navigates directly to that message (not just the inbox).

_Migrated from `LOTUS_TESTING.md` §K on 2026-09-17 — the file is now reference-only._ **How to report:** tick each item as it passes; on FAIL comment with what you saw vs expected, browser/OS, web (chat.lotusguild.org) vs desktop (Tauri), theme, and any browser-console errors. Screenshots for anything visual. **Checklist** - [ ] K1. Remind Me Later - [ ] K2. Advanced search filters (P4-9) - [ ] K3. Notification content + click target (P5-20 partial) --- ### K1. Remind Me Later On a message, **··· → Remind Me**, pick a short preset (the 20-min one, or wait one out). **Expected:** when due, a Lotus toast fires linking to that message; the reminder then clears itself. Survives a reload while pending (stored in account data). ### K2. Advanced search filters (P4-9) In message search: use the **sender picker** (instead of typing `from:@user`), the **date-range** quick presets (Today / Last week / Last month / Last year), and the **Has link** toggle. **Expected:** each narrows results correctly and reflects in the search. ### K3. Notification content + click target (P5-20 partial) Trigger a desktop/browser notification for a new message. **Expected:** it shows the **real message body** (`username: message`, not "New inbox notification from…"); **clicking it** brings the window to front and navigates **directly to that message** (not just the inbox). ---

jared added this to the Manual QA backlog milestone 2026-09-17 23:24:08 -04:00

jared added the area: messaging area: notifications qa labels 2026-09-17 23:24:08 -04:00

jared commented

2026-09-18 19:04:46 -04:00

Verified on the local dev homeserver with Playwright:

check	result
K1 Remind Me	⋯ → Remind Me → Custom time (+2.5 min) → `io.lotus.reminders` account data holds the reminder; survives a reload (still pending on the server); fires as a Lotus toast "Reminder · · Busy Room" 14 s after the due minute (30 s check interval); clicking the toast navigates straight to the message; the reminder is removed from account data ✓
K2 sender picker	From → bob → Save → results only from bob, URL carries `senders=@bob:localhost` ✓
K2 date presets	Today / Last week / Last month / Last year offered; Today sets `fromTs`/`toTs` in the URL and returns results ✓
K2 Has link	toggle applies (linked results kept); the seed data had no unlinked message matching the same term, so narrowing itself was not demonstrated here — the filter logic is unit-tested
K3 notification content	with the window unfocused: OS notification title = room name, body = `bob: notify body check 42`, tag = room id, `data.path` = the message permalink ✓; its click handler navigates directly to that message (under the space route) ✓. Focused window → in-app toast with the same body ✓

One cosmetic: toasts slide in over the seasonal floating button in the bottom-right corner (screenshot on #171 shows the overlap). Closing.

Verified on the local dev homeserver with Playwright: | check | result | |---|---| | **K1 Remind Me** | ⋯ → Remind Me → Custom time (+2.5 min) → `io.lotus.reminders` account data holds the reminder; survives a reload (still pending on the server); fires as a Lotus toast "Reminder · <message body> · Busy Room" 14 s after the due minute (30 s check interval); clicking the toast navigates straight to the message; the reminder is removed from account data ✓ | | **K2 sender picker** | From → bob → Save → results only from bob, URL carries `senders=@bob:localhost` ✓ | | **K2 date presets** | Today / Last week / Last month / Last year offered; Today sets `fromTs`/`toTs` in the URL and returns results ✓ | | **K2 Has link** | toggle applies (linked results kept); the seed data had no unlinked message matching the same term, so narrowing itself was not demonstrated here — the filter logic is unit-tested | | **K3 notification content** | with the window unfocused: OS notification title = room name, body = `bob: notify body check 42`, tag = room id, `data.path` = the message permalink ✓; its click handler navigates directly to that message (under the space route) ✓. Focused window → in-app toast with the same body ✓ | One cosmetic: toasts slide in over the seasonal floating button in the bottom-right corner (screenshot on #171 shows the overlap). Closing.

jared closed this issue

2026-09-18 19:04:46 -04:00

jared referenced this issue

2026-09-18 19:22:08 -04:00

Seasonal floating button sits above modals and toasts (bottom-right) — should hide behind overlays #215

jared referenced this issue

2026-09-18 19:27:26 -04:00

[QA] §R Discovery-pass fixes DP1–DP18: correctness, a11y/UX, TDS colours, refactor regression pass #187

Sign in to join this conversation.