PDF: verify form-filling end-to-end #155

New issue

Open

opened 2026-04-26 08:24:32 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 08:24:32 +00:00

Member

Form-filling is structurally different from a regular documentOpen -> Editor.bin -> save round-trip because form values live in a structured layer on top of the document. If save-back doesn't preserve form fields specifically, users would lose work in a way #147's generic save-back test wouldn't catch.

Acceptance

Seed a PDF that contains at least three field types (text, checkbox, signature).
E2E test: open the PDF, fill each field, force-save (or rely on auto-save), close, reopen, assert each field's value is what we entered.
Confirm permissions.fillForms (and any related flag) is set in build_editor_config for PDFs.

OnlyOffice's Forms tab is loaded for PDFs (visible in our test screenshots — Signature, Email Address, Phone Number, ZIP Code, Credit Card, Complex Field, etc.). What happens when a user actually fills a PDF form, saves, closes, and reopens has never been verified. Form-filling is structurally different from a regular `documentOpen -> Editor.bin -> save` round-trip because form values live in a structured layer on top of the document. If save-back doesn't preserve form fields specifically, users would lose work in a way #147's generic save-back test wouldn't catch. ## Acceptance - Seed a PDF that contains at least three field types (text, checkbox, signature). - E2E test: open the PDF, fill each field, force-save (or rely on auto-save), close, reopen, assert each field's value is what we entered. - Confirm `permissions.fillForms` (and any related flag) is set in `build_editor_config` for PDFs.