GET or POST: What Happens When a Form Is Submitted
Two methods, two very different places for your data. Learn which to use, what is safe in a URL, and why neither is encrypted on its own.
The HTML markup language.
113 notes tagged
Two methods, two very different places for your data. Learn which to use, what is safe in a URL, and why neither is encrypted on its own.
The browser can check most of a form before it is sent, with no JavaScript. Learn the attributes, the CSS hooks, and why none of it replaces server va...
Three button types, one attribute, and a default that causes more accidental submissions than any other rule in HTML.
Three controls with their own rules: a textarea whose value is its content, a file input that needs the right enctype, and hidden fields that are not...
Dropdowns done properly: grouping options, multiple selection, the placeholder option trick, and when a datalist beats a select.
Checkboxes for many answers, radios for one. The name attribute is what groups radios, and fieldset with legend is what makes either group make sense.
A label names a field for every reader and grows its click target. Two ways to bind one, and the reasons a form without labels is not usable.
One element, more than twenty types. Choosing the right one gives you the correct mobile keyboard, free validation and better autofill, at no cost.
Every form is a container, a set of named controls and a submit button. Learn what action and method do, why name matters more than id, and what the b...
A table with eight columns cannot fit on a phone. Four patterns that keep the data usable, and the trade off each one makes.
A table a screen reader can read is a table with named headers. scope handles simple tables, headers and id handle the hard ones.
One cell covering several columns or rows. Simple to write, easy to get wrong, and the arithmetic has to balance or the whole grid tears.