Open code, practice, and notes →
Download source with English comments · for reading
Playwright · 15 Keyboard Navigation
Series contents · Technology map
Stage: Asynchrony, Isolation, and Diagnosis · External example · preview instructions · Storage ID: playwright-step-15
Goals and learning outcomes
- Learning outcome: explain the role of Keyboard path. Input cases: Tab·Enter·Escape.
- Deliverable: activeElement and dialog state at each step. Explain the rationale for handling Focus, linking it to the code.
Prerequisites
Prepare the experiment results for Round-trip contract and Isolation from Unit 14, “Saving, Downloading, and Restoring”.
Key concepts and explanations
Keyboard path
Tab and Enter find different defects from pointer input. Clicking alone does not prove operability.
Focus
After closing a dialog, focus must return to its invoking button so the flow can continue. Also check whether focus moves to obscured elements.
Practice setup
First check the execution scope guidance on the example screen. The following describes the environment needed to extend the assignment in a separate project. Write and run all tests in a separate Node project using @playwright/test and a dedicated local test origin. The existing playwright-01·02·03 previews only display test source; they do not run Playwright in the iframe. Write new test files yourself for the assignments and judge whether they pass only from actual runner output. Do not use a user profile or storage used for everyday work; preserve CSP and isolation.
The linked example is a starting point. It does not implement every task below. Complete work beyond its supported scope in a separate project.
Practice tasks
- In tests/day-15.spec.ts in a separate practice project, check the table of contents, document, and close path with keyboard.press and toBeFocused. Refer to the existing Unit 1·14·28 examples only as starting points.
- Input conditions: Tab·Enter·Escape. Baseline: click. Run under the baseline conditions, then record observations and errors in notes/day-15.md.
- Variable: input; changed value: keyboard. Run again through the same input path. Deliverable to save: activeElement and dialog state at each step. Hypothesis to check: Complete the same function and restore focus. Compare it with the actual results, and record whether they agree and why they differ.
Variables to observe
| Variable | Baseline | Change | Expected change / hypothesis |
|---|---|---|---|
| input | click | keyboard | Complete the same function and restore focus. |
Predictions in this table are not measured results. Change one condition at a time and record why the actual result differs.
Completion criteria
- Required deliverable: activeElement and dialog state at each step. Results are available for both the baseline and changed conditions, allowing comparison of 2 conditions; input values and the execution environment are recorded together.
- The explanation of differences between the two conditions connects both concepts: Keyboard path and Focus. For unexpected items, at least 1 cause or reason they remain unresolved is recorded.
Self-check
- Which processing stage does Keyboard path affect in this exercise? Input cases: Tab·Enter·Escape.
- Variable: input. Hypothesis to check: Complete the same function and restore focus. Did the actual results agree with the hypothesis? Explain the evidence in terms of Focus.
Official references
- Playwright Installation and Execution
- Playwright Locators
- Playwright Assertions
- Playwright Downloads
- Playwright Visual comparisons
Linked example and execution scope
Example source · Runtime environments and limits
Runnable standalone Playwright spec and HTTP fixture; preview does not run tests.
Source code and records are not overwritten automatically. Resetting an existing example also preserves your notes.
Next learning
Previous: Saving, Downloading, and Restoring · Next: Viewport and Responsive Layout