[QA] §F Visual / theming: chat-background flicker, background vs seasonal exclusivity, picker grid #176

New Issue

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

jared commented

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

Migrated from LOTUS_TESTING.md §F 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

F1. Animated chat background — no flicker (#2)
F2. Background vs. Seasonal theme are mutually exclusive (#6)
F3. Background / seasonal picker grid layout (N81)

F1. Animated chat background — no flicker (#2)

Settings → set an animated chat background (e.g. anim-rain / anim-aurora / anim-stars). Watch the message text and composer while it animates.
Expected: smooth animation, no flickering / shimmering on message text or the composer, especially after scrolling. Note your GPU/browser if you see artifacts.

F2. Background vs. Seasonal theme are mutually exclusive (#6)

In Settings → Appearance:

Pick a chat background → confirm any seasonal theme auto-switches off.
Pick a seasonal theme → confirm the chat background auto-clears to none.
(Edge) If you have old data with both set, after reload only one should visibly apply (no double-overlay clutter).

F3. Background / seasonal picker grid layout (N81)

In Settings → Appearance, look at the Chat Background and Seasonal Theme swatch grids; resize the window narrow→wide.
Expected: swatches reflow to fill each row evenly (responsive grid), with no lopsided/orphaned last row at any width.

_Migrated from `LOTUS_TESTING.md` §F 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** - [ ] F1. Animated chat background — no flicker (#2) - [ ] F2. Background vs. Seasonal theme are mutually exclusive (#6) - [ ] F3. Background / seasonal picker grid layout (N81) --- ### F1. Animated chat background — no flicker (#2) Settings → set an **animated** chat background (e.g. anim-rain / anim-aurora / anim-stars). Watch the message text and composer while it animates. **Expected:** smooth animation, **no flickering / shimmering** on message text or the composer, especially after scrolling. Note your GPU/browser if you see artifacts. ### F2. Background vs. Seasonal theme are mutually exclusive (#6) In Settings → Appearance: 1. Pick a **chat background** → confirm any **seasonal theme** auto-switches off. 2. Pick a **seasonal theme** → confirm the **chat background** auto-clears to none. 3. (Edge) If you have old data with both set, after reload only one should visibly apply (no double-overlay clutter). ### F3. Background / seasonal picker grid layout (N81) In Settings → Appearance, look at the **Chat Background** and **Seasonal Theme** swatch grids; resize the window narrow→wide. **Expected:** swatches reflow to fill each row evenly (responsive grid), with no lopsided/orphaned last row at any width. ---

theming-grid.png

184 KiB

theming-grid-mobile.png

330 KiB

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

jared added the area: appearance qa labels 2026-09-17 23:24:07 -04:00

jared commented

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

Verified on the local dev homeserver with Playwright, toggling through the real Settings UI and reading back the persisted settings:

step	chatBackground	seasonalThemeOverride
start	none	auto
pick Blueprint background	blueprint	off ✓
pick Halloween seasonal	none ✓	halloween
pick Stars background	stars	off ✓

F2 mutual exclusion holds in both directions (the write-side logic that had no unit test). F3: on a Pixel 7 profile both grids lay out in 3 columns, 76 px tiles, no horizontal overflow in the card or the document (22 background tiles, 13 seasonal tiles). F1 (animated-background flicker) is a visual/GPU judgment I can't make headless — leaving that row to your eyes.

Closing with F1 as the only unverified row.

Verified on the local dev homeserver with Playwright, toggling through the real Settings UI and reading back the persisted settings: | step | chatBackground | seasonalThemeOverride | |---|---|---| | start | none | auto | | pick **Blueprint** background | blueprint | **off** ✓ | | pick **Halloween** seasonal | **none** ✓ | halloween | | pick **Stars** background | stars | **off** ✓ | F2 mutual exclusion holds in both directions (the write-side logic that had no unit test). F3: on a Pixel 7 profile both grids lay out in 3 columns, 76 px tiles, no horizontal overflow in the card or the document (22 background tiles, 13 seasonal tiles). F1 (animated-background flicker) is a visual/GPU judgment I can't make headless — leaving that row to your eyes. ![desktop](https://code.lotusguild.org/attachments/b01de075-016d-4e8c-950c-a311ddf2fae1) ![mobile](https://code.lotusguild.org/attachments/859a4f27-5b3e-44db-aeaa-a028cc2bd676) Closing with F1 as the only unverified row.

jared closed this issue

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

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/cinny#176