Brian LeRoux šŸ’šAug 9, 2024

Forms on the web have become terrible. Lost state. No keyboard nav. Weird refreshes. Mobile hostile.

The reason is #frontend developers that think clientside state management is how to implement a form. It is not.

Good forms work without client #javascript (and then are progressive enhanced by js to work even better).

Good forms always submit. Good forms remember values and display problems inline.

How do we fix the misconceptions and, in the process, fix the forms on the web ?

Show threadmhoyeAug 9, 2024
@brianleroux There are addons that do this, but I would love browsers to have a usable short term memory for form contents by default. Maybe not 'for all time', but for maybe a week?
Show threadShadSterlingAug 9, 2024
@mhoye @brianleroux for all the things Iā€™m forced to do annually and can never remember where to find the magic incantation for some fields, Iā€™d go for 60 weeks
Show threadSlightlyCyberpunk
@ShadSterling @mhoye @brianleroux Yep. Until something like that is implemented though I personally prefer that state be saved with Javascript. I do not want a work in progress to be transmitted to the server prematurely. It should submit only when I tell it to submit. Anything else is a vulnerability.
Aug 9, 2024 at 5:47pmWeb
Show threadBrian LeRoux šŸ’šAug 10, 2024
@admin @ShadSterling @mhoye respectfully, an httponly session is not a vulnerability
Show threadmhoyeAug 10, 2024
@brianleroux @admin @ShadSterling depends on your threat model.
Show threadBrian LeRoux šŸ’šAug 10, 2024
@mhoye @admin @ShadSterling please, elaborate?