Input
- Text input
- Checkboxes and radio buttons
- Select options
- Mouse click
- Type characters
- Keys and shortcuts
- Upload files
- Focus element
#
Text inputThis is the easiest way to fill out the form fields. It focuses the element and triggers an input
event with the entered text. It works for <input>
, <textarea>
, [contenteditable]
and <label>
associated with an input or textarea.
- Sync
- Async
#
API reference- page.fill(selector, value, **kwargs)
- frame.fill(selector, value, **kwargs)
- element_handle.fill(value, **kwargs)
#
Checkboxes and radio buttonsThis is the easiest way to check and uncheck a checkbox or a radio button. This method can be used with input[type=checkbox]
, input[type=radio]
, [role=checkbox]
or label
associated with checkbox or radio button.
- Sync
- Async
#
API reference- page.check(selector, **kwargs)
- page.is_checked(selector, **kwargs)
- page.uncheck(selector, **kwargs)
- element_handle.check(**kwargs)
- element_handle.is_checked()
- element_handle.uncheck(**kwargs)
#
Select optionsSelects one or multiple options in the <select>
element. You can specify option value
, label
or elementHandle
to select. Multiple options can be selected.
- Sync
- Async
#
API reference- page.select_option(selector, **kwargs)
- frame.select_option(selector, **kwargs)
- element_handle.select_option(**kwargs)
#
Mouse clickPerforms a simple human click.
- Sync
- Async
Under the hood, this and other pointer-related methods:
- wait for element with given selector to be in DOM
- wait for it to become displayed, i.e. not empty, no
display:none
, novisibility:hidden
- wait for it to stop moving, for example, until css transition finishes
- scroll the element into view
- wait for it to receive pointer events at the action point, for example, waits until element becomes non-obscured by other elements
- retry if the element is detached during any of the above checks
#
Forcing the clickSometimes, apps use non-trivial logic where hovering the element overlays it with another element that intercepts the click. This behavior is indistinguishable from a bug where element gets covered and the click is dispatched elsewhere. If you know this is taking place, you can bypass the actionability checks and force the click:
- Sync
- Async
#
Programmatic clickIf you are not interested in testing your app under the real conditions and want to simulate the click by any means possible, you can trigger the HTMLElement.click()
behavior via simply dispatching a click event on the element:
- Sync
- Async
#
API reference- page.click(selector, **kwargs)
- frame.click(selector, **kwargs)
- element_handle.click(**kwargs)
- page.dblclick(selector, **kwargs)
- frame.dblclick(selector, **kwargs)
- element_handle.dblclick(**kwargs)
- page.hover(selector, **kwargs)
- frame.hover(selector, **kwargs)
- element_handle.hover(**kwargs)
- page.dispatch_event(selector, type, **kwargs)
- frame.dispatch_event(selector, type, **kwargs)
- element_handle.dispatch_event(type, **kwargs)
#
Type charactersType into the field character by character, as if it was a user with a real keyboard.
- Sync
- Async
This method will emit all the necessary keyboard events, with all the keydown
, keyup
, keypress
events in place. You can even specify the optional delay
between the key presses to simulate real user behavior.
note
Most of the time, page.fill(selector, value, **kwargs) will just work. You only need to type characters if there is special keyboard handling on the page.
#
API reference- page.type(selector, text, **kwargs)
- frame.type(selector, text, **kwargs)
- element_handle.type(text, **kwargs)
- keyboard.type(text, **kwargs)
#
Keys and shortcuts- Sync
- Async
This method focuses the selected element and produces a single keystroke. It accepts the logical key names that are emitted in the keyboardEvent.key property of the keyboard events:
- You can alternatively specify a single character you'd like to produce such as
"a"
or"#"
. - Following modification shortcuts are also supported:
Shift, Control, Alt, Meta
.
Simple version produces a single character. This character is case-sensitive, so "a"
and "A"
will produce different results.
- Sync
- Async
Shortcuts such as "Control+o"
or "Control+Shift+T"
are supported as well. When specified with the modifier, modifier is pressed and being held while the subsequent key is being pressed.
Note that you still need to specify the capital A
in Shift-A
to produce the capital character. Shift-a
produces a lower-case one as if you had the CapsLock
toggled.
#
API reference- page.press(selector, key, **kwargs)
- frame.press(selector, key, **kwargs)
- element_handle.press(key, **kwargs)
- keyboard.press(key, **kwargs)
#
Upload filesYou can select input files for upload using the page.set_input_files(selector, files, **kwargs) method. It expects first argument to point to an input element with the type "file"
. Multiple files can be passed in the array. If some of the file paths are relative, they are resolved relative to the current working directory. Empty array clears the selected files.
- Sync
- Async
If you don't have input element in hand (it is created dynamically), you can handle the page.on("filechooser") event or use a corresponding waiting method upon your action:
- Sync
- Async
#
API reference- FileChooser
- page.set_input_files(selector, files, **kwargs)
- frame.set_input_files(selector, files, **kwargs)
- element_handle.set_input_files(files, **kwargs)
#
Focus elementFor the dynamic pages that handle focus events, you can focus the given element.
- Sync
- Async