Fixed the SPA authentication flow
This commit is contained in:
@@ -14,6 +14,11 @@ preexisting risks are tracked in [refactoring.md](refactoring.md).
|
||||
uses `background.scripts`. Neither entry point is declared as a module.
|
||||
- Content scripts run at `document_idle`, in all matching frames on the two
|
||||
configured Fusion welcome pages. Their code also checks the hostname/path.
|
||||
- `src/auth/spa-page.js` is a separate top-frame-only SPA content script, copied
|
||||
into both distributions. It handles only extension messages for DOM readiness
|
||||
inspection and a fixed same-origin identity GET; it sends no requests on its own.
|
||||
`services/spa/page-client.js` connects this receiver to the background recovery
|
||||
flow and the existing debug envelope. No page-world script is injected.
|
||||
- There are no extension UI pages, injected page-context scripts, custom CSP,
|
||||
declared execution world, or web-accessible resources.
|
||||
- Permissions remain `cookies` and `storage`, with host access limited to the
|
||||
|
||||
Reference in New Issue
Block a user