Target actor and backup transport endpoints - #371
Merged
Conversation
|
No visual change — every screen matches the committed baselines. ✅ |
NotASithLord
force-pushed
the
codex/issue-308-actor-ports
branch
from
August 9, 2026 12:24
428af01 to
9f7e9d6
Compare
|
No visual change — every screen matches the committed baselines. ✅ |
NotASithLord
force-pushed
the
codex/issue-308-actor-ports
branch
from
August 9, 2026 12:58
9f7e9d6 to
0e136d8
Compare
Visual regression✅ No visual drift. Every state renders identically to the committed baselines. 📸 Browse the visual gallery — 54 baseline screens (light + dark) as of this commit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #308
Chrome now sends actor jobs and relays through a MessageChannel transferred to the exact offscreen document. The service worker keeps authority in a run-bound closure, and startup uses an explicit accept and commit handshake so pre-start failures are safe to retry while post-start loss stays outcome-unknown. Firefox keeps its private background-host path.
Backup and restore use the same exact-recipient pattern on Chrome. Firefox uses an exact-options background Port because it has no service-worker WindowClient API. Failed starts retain the selected backup and passphrase so the user can retry without rebuilding the form.
Security and lifecycle docs and the red-team scenario now describe the structural boundary. Browser tests cover sibling interception, ambiguity refusal, replay prevention, Firefox routing, and restore UX.