ai-elements

Fixes #439 While streaming with an handler, renders as , so the Enter guard in finds no and evaluates to : the form submits mid-stream. This applies the guard proposed in the issue: no submit button in the form blocks Enter, same as a disabled one. This also answers the behaviour question raised in the issue thread: a composable without no longer submits on Enter. The form has no submit control to consult, and submitting with unknown status is the unsafe default. Both behaviours are pinned in . All 952 package tests pass.

Memoized attachment rows re-rendered on each keystroke in provider-backed mode. The local attachments context made a new copy of each attachment object on each recompute, and each text change caused a recompute. Rows that compare attachments by reference, for example a chip, could not skip those renders. This change passes the array through by reference. Unchanged attachments keep their identity during text input, but rows still re-render when a file is added or removed. Two new tests make sure that references stay equal during text input and that a memoized chip re-renders only on file changes. The two tests are not successful before the change.

With , each keystroke removed the and listeners on the document or the form, and installed them again. The registration effect for the hidden file input also ran on each keystroke. After this change, the listeners attach one time for each mount, and text input does not touch them. The drop handlers call a wrapper, and the wrapper calls the latest closure. Thus the validation behavior for , , , and does not change. Five new tests spy on the document listeners and the form listeners during text input, and drop files after prop changes and count changes. Four of the five tests are not successful on the code before this change. The fifth test makes sure that a drop on the document adds the file. Evidence: