Style a control that fails native validation.
CSS: Invalid reflects the input’s current constraint-validation result.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Example</title>
<style>
input:invalid { border:2px solid rgb(180,30,30); } input:valid { border:2px solid rgb(30,120,50); }
</style>
</head>
<body>
<label for="email">Email</label><input id="email" type="email" required>
</body>
</html>Expected output EXAMPLE
At a 1000 × 800 CSS-pixel viewport, unless another size is stated: Enter “bad” into the “input” element. The “input” element has computed border-top-color “rgb(180, 30, 30)”. Enter “ada@example.invalid” into the “input” element. The “input” element has computed border-top-color “rgb(30, 120, 50)”.
Details
Save this complete fixture as example.html. The output describes layout or computed styles verified in Chromium. Invalid reflects the input’s current constraint-validation result.
Tested on Ubuntu 24.04.5 LTS · · Chromium 141.0.7390.37 · libc6 2.39-0ubuntu8.9; Playwright 1.56.0
Test inputs, results and environment
The exact published code ran in a dedicated Linux test container with prepared inputs. Unprivileged snippet process, external networking disabled, read-only root filesystem, and a fresh temporary working directory. Fixtures and output records are isolated from the application database. Testing covers this example and its stated checks, not every input, operating system, or runtime version. The Linux container shares its host's kernel; this is not a native Windows test.
- Architecture / host kernel
- x86_64 / 6.18.54.1-microsoft-standard-WSL2
- Snippet identity / locale
- uid=65534, gid=65534 (unprivileged) / C.UTF-8
- Interpreter invocation
Chromium: open example.html; execute the published browser assertions- Container image ID
sha256:32dc2d998158b6554c99b73b533f423696a0f3e31e8cbea9db10b5eee9a2fadd- Code SHA-256
7ada837f1a0ba4d29fb5360d929a2680d87f1c02e4b3d6bb6d2e93fd7faa8a73- Dependencies
- libc6 2.39-0ubuntu8.9; Playwright 1.56.0
Test input setup
These are the prepared inputs used by the test harness. See Details above for the prerequisites and how to run this example.
# No input files required.
Observed standard output
Expected output describes the rendered page. The standard-output record below is the browser test harness receipt; the additional assertions check the result and interactions.
Style a control that fails native validation: browser checks passed.
Exit code: 0. Standard error: empty. Validation: Shape/content assertions. System-dependent values above are one recorded run.
Additional assertions that passed
Checks recorded by the test harness. Where Python assertions are shown, browser cases use Playwright and simulator cases may inspect pin transitions: result.stdout is captured output, work is the temporary directory, and Path is pathlib.Path. The harness also imports json and csv.
await page.locator('input').fill('bad')
assert await page.locator('input').evaluate('(e)=>getComputedStyle(e).borderTopColor')=='rgb(180, 30, 30)'
await page.locator('input').fill('ada@example.invalid')
assert await page.locator('input').evaluate('(e)=>getComputedStyle(e).borderTopColor')=='rgb(30, 120, 50)'