Consistent protected-page session checks
A restored tab now waits for its own current session check, preserves unsaved work after failures, and avoids unnecessary reloads when permission lists only change order.
- Improvements and fixes
Tab and cached-page restoration: Restoration conceals private content immediately, even if a background check is pending. A check begun before the latest hide cannot reopen the page or restore background focus. One current read follows when needed, while duplicate restoration notifications share the pending current check.
- Improvements and fixes
Recovery and current authority: An older failure cannot replace a newer restoration with obsolete retry state. Current failures keep forms and private dialogs intact until a fresh successful check. Actual member or permission changes still clear and reload; missing or inactive identities cannot reopen private content. Identical permission lists compare independently of their order.
- Improvements and fixes
Existing sign-in rules retained: A fresh page continues to reuse the session verified for that exact document without another initial check. Current server authorization, verification requirements, OTP duration, inactivity rules, browser limits and periodic checks remain unchanged.
This repair governs browser concealment and read sequencing. It does not bypass sign-in, verify a phone, grant permissions, change session duration, approve records or send messages. Authenticated native restoration, mobile and independent role acceptance remain pending the existing browser handoff.