diff options
| author | Igor Soarez <igor@soarez.org> | 2026-11-06 13:49:39 +0200 |
|---|---|---|
| committer | Igor Soarez <igor@soarez.org> | 2026-11-06 13:49:39 +0200 |
| commit | 68216dcb01c8cd5894c6e2b4914d7c619d75ab35 (patch) | |
| tree | 30acabe469d623b1b23459d09cf9f8fb3cf3c6f0 /test-suite/unit/session-cleanup.test.mjs | |
| parent | 85b49885256464b735923eaa771044706383718f (diff) | |
extension: keep PI_CHROME_AUTHORIZE grants out of the persisted grant
The env grant was saved to globalThis like a /chrome authorize grant. After
a /reload or a session switch (/resume, /fork, /new) the new runtime restored
it, skipped the env branch, and left envGranted false, so the footer
announced a grant the user never gave.
Read the variable again on each session_start instead of persisting it.
A restored grant now always comes from /chrome authorize. A timed env grant
restarts its countdown on each reload or switch.
Diffstat (limited to 'test-suite/unit/session-cleanup.test.mjs')
0 files changed, 0 insertions, 0 deletions