fix(extension): resolve DSH authentication cookie conflicts in 0.1.2 - #9
Merged
Merged
Conversation
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.
Chrome could show
dsh web authentication requiredafter a user approved AgentOnWeb because an old first-party DSH cookie preceded the newly delegated partitioned cookie. Send the current session with a tab-and-port-scoped HTTP header rule while retaining partitioned cookies for WebSocket authentication. Clear stale rules when the background restarts and remove both delegations on revocation.Release the browser extension as 0.1.2; the DSH npm plugin remains 0.1.1. Chrome adds
declarativeNetRequestWithHostAccess; Firefox keeps its existing cookie path. Includes a repeatable real-browser regression and diagnosis/acceptance notes.Validation:
pnpm release:auditpassed (86 tests, 1 existing skip), typecheck, privacy/architecture checks, all browser builds, native Safari manifest validation and reproducible packages. Real-browser conflicting-cookie regression passed with DSH 0.1.2-alpha.3 and 0.1.5-rc.3. Computer Use on real YouTube verified native approval, page refresh/reopen and extension reload/reconnect with DSH 0.1.5-rc.3. No model turn was sent.