🐛 - Bugbot reports that FormData rejects a null submitter and overlooks the remaining reset control #900

Is there an existing issue for this?

• I have searched the existing issues.

Which actions are affected?

Pull Request

Which platforms are affected?

No response

Description

The finding says that the installed React and Svelte form fixtures crash when Enter implicitly submits after the only submit button is hidden. The exact handler accepts the real null submitter in FormData, and the separate reset control is still mounted with its own native proxy. The complete installed-browser journey passes in React, Vue, Angular and Svelte. Expected: validate both the browser API and the complete form before publishing a crash claim, and reconcile the finding without requiring an unrelated runtime change.

Reproducing the issue

1. At ha-ui head 41b84aa337f829e3c17b1ea1e1ef5ec54fd98443, run the packed app fixture and leave Kitchen in the valid task field.
2. Activate Toggle action button to remove #bound-submit. Reset task stays mounted.
3. Focus the task field and press Enter. The real submit event reports submitter === null, the submitted entries are [["task","Kitchen"]], and the fixture correctly reports that no button provided metadata. There is one submission and no press request or exception.
4. Independently run new FormData(document.createElement("form"), null) in the same Chromium browser. Construction succeeds. The installed-consumer regression exercises the complete path in all four frameworks.

copilot Version

v3 (3e7ceea)

Relevant Log Output

Additional context and comments

Exact review run. This is distinct from #897, which concerned how a different default submitter is discovered when two blocking fields exist.