Forms that submit, and a faster one to fill in
Two question types shipped in earlier releases could be answered but not submitted: a respondent picked their country, pressed send, and was told to fix a field they had filled in correctly. The same went for anything typed into “Other, please specify”. Both are fixed, with tests that fail without the fix. The rest of the release is weight and waiting — the public form now caches its published copy and no longer sends the error-reporting bundle to the person filling it in.
Country and state questions submit
A form asking for a country or a US state could not be completed by anyone — the answer was checked against an empty list and always refused. Any form built from the application template was affected.
“Other, please specify” is accepted
A respondent who chose Other and typed their answer had it rejected as an invalid selection, after they had already written it.
A lighter, faster public form
The error-reporting bundle — around 150 KB, roughly half of what loaded before the first question appeared — is no longer sent to respondents, and the published form is cached between requests instead of being rebuilt for every visitor.
Built for a thumb
Every control on a live form now has a 44px tap target and 16px text, so iOS stops zooming in when a field is focused, and the Studio canvas no longer reserves desktop height for text that wraps shorter on a phone.
A render error no longer blanks the form
If a single question fails to draw, the form says so and keeps going instead of showing an empty page, and every field control now carries a name for screen readers.