| Filename | Latest commit message | Latest commit date |
|---|---|---|
6c6d6f67e7
When a question_added or question_resolved SSE event fires, the handler calls renderQuestions() directly — bypassing the snapshotOpenDetails / restoreOpenDetails pair that refreshState wraps around it. This caused the answered-history <details> (data-restore-key="q-history") to collapse every time a question arrived or was resolved while the operator had it open. Fix: call snapshotOpenDetails() at the start of renderQuestions() and restoreOpenDetails() at the end. The double-restore in the refreshState path is harmless — re-opening an already-open <details> is idempotent, and restoreOpenDetails is a no-op when the snapshot set is empty. |
||
| .. | ||
| src | ||
| build.mjs | ||
| package.json | ||