An email input with multiple accepts a comma-separated list of email addresses for one named control.
Make this comfortable
HTML multiple email input: parse a list, not a single address
Why this choice matters
A service desk invites several depot contacts to one maintenance update. The field label says multiple addresses are allowed and the visible help states how to separate them. A browser syntax check can reject malformed entries, but it cannot confirm that an address belongs to the intended person, prevent a typo from contacting someone else, or establish consent to send a message. The server must split, normalize, and apply its own recipient-count policy before dispatch.
<form action="/updates/maintenance/invite" method="post">
<label for="recipient-emails">Depot contacts to invite</label>
<p id="recipient-help">Separate addresses with commas; maximum three recipients.</p>
<input id="recipient-emails" name="recipients" type="email" multiple required aria-describedby="recipient-help">
<button type="submit">Review invitations</button>
</form>What it does not do
The stated maximum of three is a server rule; multiple by itself does not impose it. The next page should show the parsed recipients before any external message is sent.
Cost and operational limits
The native control is light. Recipient parsing, deduplication, consent checks, and error handling are the real work, especially when a malformed entry appears in the middle of a list.
Common Mistakes
- Do not assume multiple sets a recipient-count limit.
- Do not send invitations solely after browser syntax validation.
- Do not hide the comma-separation rule in placeholder text.
Connected lessons
html
forms