The symptoms sound very similar to this issue: #177248

When the hidden input's value is updated, does it receive focus first or does it get updated without a focus event?

The symptoms sound very similar to this issue: #177248

When the hidden input's value is updated, does it receive focus first or does it get updated without a focus event?

1. I measured it on a real iOS Chrome device with a focusin/input probe: the hidden password input is updated
   without a focus event. The browser fires input and change on it while document.activeElement stays on
   the focused username field, and no focusin ever lands on the password field.

2. Different failure mode from [web] Autofill does not work on browsers running on iOS 26 and iPadOS 26 devices #177248 though. That one is total autofill failure on iOS 26 across browsers; here autofill partially works, the focused username fills but the non-focused password is lost on iOS Chrome, while iOS Safari fills both.

1. the hidden password input is updated
   without a focus event. The browser fires input and change on it while document.activeElement stays on
   the focused username field, and no focusin ever lands on the password field.

This case is supposed to be handled by:

1. the hidden password input is updated
   without a focus event. The browser fires input and change on it while document.activeElement stays on
   the focused username field, and no focusin ever lands on the password field.

This case is supposed to be handled by:

flutter/engine/src/flutter/lib/web_ui/lib/src/engine/text_editing/text_editing.dart

Lines 442 to 456 in 8cffb53

	subscriptions.add(
	DomSubscription(
	element,
	'input',
	createDomEventListener((DomEvent e) {
	if (items[key] == null) {
	throw StateError('AutofillInfo must have a valid uniqueIdentifier.');
	} else if (key != focusedElementId) {
	// `input` events on the focused element are handled elsewhere.
	final AutofillInfo autofillInfo = items[key]!.autofillInfo;
	_handleChange(element, autofillInfo);
	}
	}),
	),
	);

Yes, that path should handle non-focused input events while the form is active.

The difference here is timing: in this repro, the password appears to be written after DefaultTextEditingStrategy.disable() has canceled the autofill input subscriptions, but while goDormant() keeps the form in the DOM for browser autofill. So the DOM input gets the password, but Flutter no longer has that listener attached to call _handleChange.

Then when the dormant form is reused, wakeUp() calls _updateFieldValues(), which previously copied the framework's stale empty value back into the non-focused password input.

autosubmit label was removed for flutter/flutter/187459, because The base commit of the PR is older than 7 days and can not be merged. Please merge the latest changes from the main into this branch and resubmit the PR.