The commissioning decision
A training provider assumes that a green email field means course details will reach the applicant. The browser can accept a well-formed address at a reserved example domain that has no customer mailbox. Separate format validation, mailbox confirmation and message delivery in the enquiry acceptance record.
Source and claim boundary
The email input validates address syntax, not whether that mailbox exists or belongs to the visitor. Browser checks cannot serve as security verification. MDN · Checked 16 October 2026.
Filled synthetic acceptance cases
Synthetic teaching data, not client records. Review the inputs and expected outcomes before running the isolated browser exercise. On narrow screens, scroll the table.
| Input | Check | Expected |
|---|---|---|
| learner@example.invalid | Native syntax validation | Pass; delivery still unknown |
| not-an-address | Native syntax validation | Fail |
| Empty required field | Native validation | Fail |
How to verify beyond appearance
- Define separate states for format accepted, ownership checked and delivery outcome.
- Replay the fixture with reserved-domain synthetic addresses only.
- Use authorised test mailboxes for integration, retain provider outcomes and do not treat queued as delivered.
Interpret the result
The useful result is a narrower claim: a syntax pass permits the next step, not a promise of contact. A provider acceptance, a bounce and an ownership-confirmation click answer different questions. Record each timestamp and scope independently. The fixture never sends mail and cannot establish a real recipient, consent or an enquiry conversion.
What this does not prove
Internationalised-address support, provider restrictions and anti-abuse controls require separate current evidence. No real email address is collected.
Runnable fixture and handover record
Open the browser acceptance fixture · Read the test source。The fixture creates temporary elements with synthetic values inside the browser. It reads no account, uploads no file, and sends no email or form. Record the browser version, check name, observed value and pass state. Keep real integration evidence separate: a local pass is not a live delivery result.