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 ?

@brianleroux first, I would get rid of your assumption that it is "front end devs" responsible for this

Many (most) forms are created by "full stack" devs who - speaking for myself - never had a day of training on best practices & work things out to the best they can, following instructions from a manager with no formal UX experience

Looking at the problem from that POV changes the answer quite a bit

@codebyjeff I'm not entirely sure what a fullstack is or how a dev becomes one but the only devs I hear talking about or claiming that particular title are squarely in the FE frameworks side of things

@brianleroux you become one by being a database programmer and having your manager say,

"Great! Can you fix the responsiveness on this web page?"

And joking aside, that's what I mean in saying many of us are doing a job we were not trained for, and don't even realize when we aren't following best practices