orke browser page.wait
Wait for text, URL, element, or loading conditions.
When to use it
Wait for text, URL, element, or loading conditions.
Usage
Syntax · [ ] marks optional arguments
orke browser page.wait [--text <string>] [--url <string>] [--element <string>] [--load <boolean>] [--visible <boolean>] [--state <visible|hidden|enabled|disabled|editable|readonly|checked|unchecked|detached>] [--value <string>]Options
| Options | Required? | Value and description |
|---|---|---|
--text | Optional | Original text to enter or save. |
--url | Optional | URL to open or navigate to. |
--element | Optional | Element reference from the latest snapshot or current run observation. |
--load | Optional | true waits for loading to finish. |
--visible | Optional | Whether the condition must be visible. |
--state | Optional | visible | hidden | enabled | disabled | editable | readonly | checked | unchecked | detachedElement state, such as visibility, enabled, editable, or checked. |
--value | Optional | Option value to save, or input value to wait for. In set-run-option, omitting it removes the line. |
Common management options and errors →
Example
Terminal
orke browser page.wait --page "page_ID" --text "Done" --visible true --jsonReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
Read both ok and error, and check the actual IDs, states, and partial results in data.
Behavior and states to watch
- Use --page to specify the target. If the target is ambiguous, select an ID from tab.list.
- Specify conditions with text, url, element, or load. Use element states and values (state, value) together with element. Waiting does not enter input.