You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: prevent fullscreen stack buildup during arrow-key grid navigation
The browser Fullscreen API is a stack — every requestFullscreen() call
pushes a new entry and exitFullscreen() only pops the top. The previous
arrow-key navigation called nextCell.requestFullscreen() directly, so
visiting streams A→B→C→D built up a hidden stack [A,B,C,D]. Exiting
fullscreen then required unwinding every visited stream one-by-one before
returning to the grid (double-click / toggle button / Escape each only
removed the topmost entry).
Fix: always call document.exitFullscreen() first to drain the stack to
empty, wait for the fullscreenchange event to confirm the transition, then
call requestFullscreen() on the next cell. A module-level _fsNavBusy
guard prevents overlapping transitions from rapid key presses.
Closes #317
0 commit comments