- Text input
- Checkboxes and radio buttons
- Select options
- Mouse click
- Type characters
- Keys and shortcuts
- Upload files
- Focus element
This 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
<label> associated with an input or textarea.
- page.fill(selector, value, **kwargs)
- frame.fill(selector, value, **kwargs)
- element_handle.fill(value, **kwargs)
#Checkboxes and radio buttons
This is the easiest way to check and uncheck a checkbox or a radio button. This method can be used with
label associated with checkbox or radio button.
- page.check(selector, **kwargs)
- page.is_checked(selector, **kwargs)
- page.uncheck(selector, **kwargs)
Selects one or multiple options in the
<select> element. You can specify option
elementHandle to select. Multiple options can be selected.
- page.select_option(selector, **kwargs)
- frame.select_option(selector, **kwargs)
Performs a simple human click.
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
- 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 click
Sometimes, 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:
If 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:
- page.click(selector, **kwargs)
- frame.click(selector, **kwargs)
- page.dblclick(selector, **kwargs)
- frame.dblclick(selector, **kwargs)
- page.hover(selector, **kwargs)
- frame.hover(selector, **kwargs)
- page.dispatch_event(selector, type, **kwargs)
- frame.dispatch_event(selector, type, **kwargs)
- element_handle.dispatch_event(type, **kwargs)
Type into the field character by character, as if it was a user with a real keyboard.
This method will emit all the necessary keyboard events, with all the
keypress events in place. You can even specify the optional
delay between the key presses to simulate real user behavior.
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.
- page.type(selector, text, **kwargs)
- frame.type(selector, text, **kwargs)
- element_handle.type(text, **kwargs)
- keyboard.type(text, **kwargs)
#Keys and shortcuts
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
- Following modification shortcuts are also supported:
Shift, Control, Alt, Meta.
Simple version produces a single character. This character is case-sensitive, so
"A" will produce different results.
Shortcuts such as
"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
Shift-A to produce the capital character.
Shift-a produces a lower-case one as if you had the
- page.press(selector, key, **kwargs)
- frame.press(selector, key, **kwargs)
- element_handle.press(key, **kwargs)
- keyboard.press(key, **kwargs)
You 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.
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:
- page.set_input_files(selector, files, **kwargs)
- frame.set_input_files(selector, files, **kwargs)
- element_handle.set_input_files(files, **kwargs)
For the dynamic pages that handle focus events, you can focus the given element.