From f1bf2d1e892fe6f93b4d618c6d12f3589da6bf47 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Wed, 18 Nov 2026 13:45:33 +0100 Subject: 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 --- CHANGELOG.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 6c9c6fee..4a8c99b6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,10 @@ All notable changes to this project will be documented in this file. - About: "Report a security issue" links to the security policy, with the maintainer's OpenPGP key for private reports +### Fixed + +- Autofill in Vanadium: fill was never offered, because Vanadium's native autofill labels every field with its page origin, which the single-origin check rejected. Vanadium now uses per-field origins (an iframe's form gets the iframe's origin) and offers to save new logins + ## [0.3.4] - 2026-11-09 ### Added -- cgit v1.2.3