diff options
| author | Danilo M. <danix@danix.xyz> | 2026-11-18 13:45:33 +0100 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-11-18 13:45:33 +0100 |
| commit | f1bf2d1e892fe6f93b4d618c6d12f3589da6bf47 (patch) | |
| tree | ceaff9ec4b557ba2b44e940dd62d3259a50e8842 /app/src/main/res/layout/activity_git_clone.xml | |
| parent | 477c5d2aa08814b9c1b0611b62c16b7899f075b2 (diff) | |
| download | HardenedPass-f1bf2d1e892fe6f93b4d618c6d12f3589da6bf47.tar.gz HardenedPass-f1bf2d1e892fe6f93b4d618c6d12f3589da6bf47.zip | |
autofill-parser: fix Vanadium fill with per-field origins
Vanadium (Chromium 157, "Autofill using another service") annotates
every form field with its frame's web origin. Vanadium had no multi
origin method, so it ran in single origin mode, which requires fillable
fields to carry no origin: every scenario failed the origin check and
no fill was offered.
Use BrowserMultiOriginMethod.Field. Checked on a Pixel 6 Pro with a top
page on 127.0.0.1 and a login iframe on localhost: each form reports
its own frame's origin, and Chromium sends only the focused form. Save
flag 0 is enough: the system save prompt appears on submit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'app/src/main/res/layout/activity_git_clone.xml')
0 files changed, 0 insertions, 0 deletions
