Events and forms
Bind form controls
Use x-model with text, checkbox, radio, select, and modifiers while preserving labels and native form behavior.
9 minute lesson
Start from the behavior you can observe. The issue editor keeps labeled native controls and can submit normally if the enhanced request path fails.
x-model synchronizes control values with state, but accessible HTML and browser submission semantics still matter. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.
It is tempting to replace real controls with clickable div elements because binding looks shorter. That trades a clear decision for an assumption you will eventually have to debug. The stronger move is to bind native labeled controls, choose value types deliberately, and keep the form action meaningful. Make the boundary explicit in code and in the project notes.
Tie the decision back to the larger job: Build a keyboard-usable issue editor whose state, validation, and submission lifecycle remain explicit. Record enough evidence that another developer can repeat the result without relying on your memory.
Bind all filter control types and inspect the state values, submitted values, and behavior without JavaScript. Repeat it once with an invalid or hostile condition and write down the boundary the failure revealed.
Lesson completed