Skip to main content

Module interaction

Module interaction 

Source
Expand description

Pointer, keyboard, form, and dialog interaction over CDP.

§Workload

I/O-bound ordered: clicks, keys, type (char-a-char), drag paths, and fill-form fields must stay sequential on one Page (N-135/N-141). Parallel input races focus and breaks DOM semantics. No JoinSet fan-out here.

Structs§

ClickResult
Outcome of a click. dialog_opened is true if a JavaScript dialog opened mid-sequence (the page is then blocked until dialog accept/dismiss). pending_release is set only when the dialog opened after mousePressed but before mouseReleased: the button is logically held until the caller dispatches the release (done once the dialog is resolved), otherwise the next click would register as a drag or double-click.
PendingRelease

Functions§

check
clear
click
click_at
Click at page coordinates (vision / experimental path).
dblclick
dispatch_event
dispatch_pending_release
Best-effort mouseReleased to clear a button left logically down when a dialog opened mid-click. Called after the dialog is resolved.
drag
Drag from one element center to another via CDP mouse events.
fill
fill_smart
Smart fill matching DevTools agent fill semantics:
focus
highlight
hover
press_key
press_key_with_modifiers
Dispatch a keyDown+keyUp sequence for key with an optional CDP modifier bitmask.
scroll
scroll_into_view
select_all
select_option
tap_touch
type_text
type_text_into_active_context
uncheck