Fill in a form in the browser

[tannevaled]

A form is the one thing in a PDF meant to be changed by whoever receives it — and the one thing every other verb in this workbench would destroy, since rotating a page or laying two on a sheet rebuilds the document and a form is tied into one by object number in a dozen places at once.

So a form is filled in on the file itself: what was opened is kept, the values go into it, and what is saved is that file with the answers appended. A form saved here is still a form.

Built from the toolkit, nothing hand-drawn

Entry for a text field, CheckButton for a checkbox or a button, DropDown for a choice field, FormField for the label, ScrollView for a form longer than the window. A field the document locks is shown as a plain label — so somebody can read what it holds and see why they cannot type in it.

Each is bound to its field through the observable the widget already publishes. Nothing is copied per frame.

What the tests taught me

The first version of these tests called Field.SetText directly and passed — while three of the bindings had never once been executed. Coverage said so; the assertions did not.

They now dig the real widget out of the row and drive that:

entry := inputOf(t, s.form.row(s, field)).(*toolkit.Entry)
entry.SetText("Mozart")
if field.Value != "Mozart" { ... }

Which is the difference between proving the setter works and proving anything is wired to it.

100% statement coverage, go vet clean, js/wasm builds.