Skip to content

docs: correct & clarify how ancillary events are dispatched during keyDown/Up patterns #6259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: release/15.1.0
Choose a base branch
from
Open

docs: correct & clarify how ancillary events are dispatched during keyDown/Up patterns #6259

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
355f62b
clarify behavior of keypress/input events
cacieprins Aug 25, 2025
8e0377e
clarify
cacieprins Aug 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/api/commands/press.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ componentSpecific: false

Trigger native key events in your application to simulate keyboard interactions.

A `keydown`, `press`, and `keyup` event will be dispatched directly to the browser window.
A `keydown` and `keyup` event will be dispatched directly to the browser window. If an input changes due to these events, the proper `input` event will be dispatched.

Unlike `cy.type()`, which is best for typing multiple character keys, `cy.press()` will dispatch real keyboard events rather than simulated ones. This command is especially useful when testing focus management and keyboard navigation patterns which are critical for [accessibility testing](/app/guides/accessibility-testing) and great keyboard UX.

Expand Down