Allow one disclosure in a named group to stay open.
HTML: Matching details name attributes create an exclusive native accordion in supporting browsers.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Example</title>
</head>
<body>
<details name="help"><summary>First</summary><p>One</p></details><details name="help"><summary>Second</summary><p>Two</p></details>
</body>
</html>Expected output EXAMPLE
Open First, then Second. Second expands and First closes, so only one explanation in the named group remains open.
Details
Save as example.html and open in a modern browser. The output describes browser behavior verified with DOM and interaction assertions. Matching details name attributes create an exclusive native accordion in supporting browsers.
Uses native named details groups supported by current major browsers; test older target browsers before relying on exclusivity.
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
bea801843b0071f84c395713a8e4c899974151d3b62ee242fce0f9d987237201- 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.
Allow one disclosure in a named group to stay open: 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.get_by_text('First',exact=True).click()
await page.get_by_text('Second',exact=True).click()
assert await page.locator('details').nth(0).evaluate('(e)=>e.open') is False
assert await page.locator('details').nth(1).evaluate('(e)=>e.open') is True