Skip to main content

Module page

Module page 

Expand description

Typed requests against a live page’s content.

Browser chrome turns its page actions into a PageRequest; the engine answers with exactly one WebViewEvent::PageResult carrying the same request id. Elements are addressed by the refs a prior PageRequest::Outline printed. A ref names one element of one document, so a ref from a page the tab has since left is refused rather than resolved against whatever now sits at the same position.

Structs§

PageFailure
Why a page request did nothing. code is stable, such as stale_element, obscured or unavailable.
PageKey
One key plus modifiers, written as a chord such as Enter, Shift+Tab or Control+a.
PageReply
What a completed page request observed.

Enums§

PageRequest

Constants§

MAX_DATA_BYTES
Upper bound on structured reply data (PageReply::data), serialised.
MAX_FILL_BYTES
Upper bound on the text one fill may insert.
MAX_OUTLINE_BYTES
Upper bound on an outline as it crosses the engine boundary.
MAX_SELECT_VALUES
Upper bound on the options one select may choose.
MAX_SELECT_VALUE_BYTES
Upper bound on one option value or label.
MAX_SETTLE_MS
MIN_SETTLE_QUIET_MS
Bounds of a settle wait, milliseconds.

Functions§

is_element_ref
Element refs are d<document>e<element>: both parts are decimal, so a ref can never smuggle selector or script syntax to the engine.