fix: constrain AllowUniversalAccessFromFileURLs to file: origins in agent cluster key assignment#50789
Conversation
c44f2d2 to
2f71022
Compare
|
Possible to add a regression test on our end based on the gist from the issue ? |
codebytere
left a comment
There was a problem hiding this comment.
@clavin could you also link the CL so we know what upstream thinks before we merge this?
jkleinsc
left a comment
There was a problem hiding this comment.
requesting changes until a test is added and an upstream CL is linked.
|
crbug filed: https://crbug.com/505299810 CL soon |
|
CL: https://chromium-review.googlesource.com/c/chromium/src/+/7795303 next up: rebasing on main to resolve the merge conflict, linking to the CL in the patch description |
b4cfe20 to
d970d5b
Compare
|
mergers: ready to land! edit: test added too! |
…gent cluster key assignment Fixes #50242 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
d8198f5 to
c79bb99
Compare
|
Release Notes Persisted
|
|
I have automatically backported this PR to "41-x-y", please check out #51403 |
|
I have automatically backported this PR to "42-x-y", please check out #51404 |
Description of Change
tl;dr: Adds a patch that fixes
window.crossOriginIsolatedfor non-file:origins. I intend to upstream it.Fixes #50242
Credit to @deepak1556 for identifying the regression source and suggesting the split approach in #50242
Verification
Tested with the gist repro from the issue. Also verified programmatically (red/green testing): a recent v43 nightly reports
crossOriginIsolated: false, the patched build reportstrue.Checklist
npm testpassesRelease Notes
Notes: Fixed cross-origin isolation failing for non-file origins.