siftlode/frontend
npeter83 3d8015f3a9 fix(history): stop the next overlay's first Back being swallowed after a button/ESC close
useBackToClose closes an overlay programmatically (X button or ESC) by
setting the module-global suppressPop=true and calling history.back(), so
the remaining overlays' popstate handlers ignore that synthetic pop. But
the flag was only ever reset by one of those handlers — when the closed
overlay had no overlay underneath it (the common single-player case),
nothing consumed it and suppressPop leaked true.

The next overlay's first real Back then hit the stale true, reset it and
returned early without closing — the Back was silently swallowed. Symptom
in the YouTube-search flow: close the player with the X button, open
another, press Back once -> nothing happens; a second Back closes it AND
discards the search results, dumping you on the normal feed.

Fix: register a one-shot popstate listener alongside suppressPop=true so
the flag is cleared on that very pop even when no overlay remains to
consume it. Nesting is unaffected (an underlying overlay still short-
circuits first and the one-shot is a redundant no-op).
2026-07-01 01:42:00 +02:00
..
public/welcome feat(welcome): landing lightbox, prod-served screenshots & session-end UX 2026-06-19 19:52:29 +02:00
src fix(history): stop the next overlay's first Back being swallowed after a button/ESC close 2026-07-01 01:42:00 +02:00
index.html chore: rebrand Subfeed -> Siftlode 2026-06-14 04:40:22 +02:00
package-lock.json feat(feed): virtualize the feed list and consume the keyset cursor 2026-06-25 19:54:40 +02:00
package.json feat(feed): virtualize the feed list and consume the keyset cursor 2026-06-25 19:54:40 +02:00
postcss.config.js feat: M4 (part 2) — React reader UI with theming 2026-06-11 02:19:47 +02:00
tailwind.config.js feat: M4 (part 2) — React reader UI with theming 2026-06-11 02:19:47 +02:00
tsconfig.json feat: M4 (part 2) — React reader UI with theming 2026-06-11 02:19:47 +02:00
vite.config.ts fix(dev): vite proxy to 127.0.0.1 + throttle error notifications 2026-06-11 22:00:57 +02:00