It'd be possible to store the decrypted member list et al in sessionStorage. It'd also be possible to erase that memory (ie. auto-close sign-in) after a period of activity, or after the event closes (see #14), so long as the page is open.
The main reason I don't want to do the former is that I think this allows for a closed tab in a long-lived browser session to inadvertently persist the membership list - also, I don't think there's anything in-spec that says sessionStorage necessarily won't be persisted to disk somehow (like for crash recovery or something).
It's worth noting, though, that persisting that data would also make it smooth-sailing to have the page refresh on update, restoring all possible state. (Kind of a far-flung feature, though.)
It'd be possible to store the decrypted member list et al in
sessionStorage. It'd also be possible to erase that memory (ie. auto-close sign-in) after a period of activity, or after the event closes (see #14), so long as the page is open.The main reason I don't want to do the former is that I think this allows for a closed tab in a long-lived browser session to inadvertently persist the membership list - also, I don't think there's anything in-spec that says sessionStorage necessarily won't be persisted to disk somehow (like for crash recovery or something).
It's worth noting, though, that persisting that data would also make it smooth-sailing to have the page refresh on update, restoring all possible state. (Kind of a far-flung feature, though.)