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 ?

We teach how to do this properly on https://enhance.dev but we are only one of many different frameworks..and the techniques SHOULD be framework agnostic. That said, many frameworks conveniently ignore POST unless it's client fetch. Which is cheesy.
Enhance

The HTML first full stack web framework

Enhance

Two other notes.

1. Luke W has THE book on design of forms here https://www.lukew.com/resources/web_form_design.asp

2. Most of this is downstream frontend frameworks ignoring POST so they don't need to teach/handle httponly session state for persisting values. Arguably these types of framework are a poor choice for UX.

LukeW | AI Has Flipped Software Development

For years, it's been faster to create mockups and prototypes of software than to ship it to production. As a result, software design teams could stay "ahead" of...

@brianleroux this stuff is so crazy… like it is a damn form, one of the oldest things. why do people do these wrong?
@sayrer the boot camp industrial complex and YouTube influencer education depend on "break into tech" content being primarily about GET requests so they can skip anything backend. At least that's my theory. Cc @slightlyoff @polotek