1.1 Dependencies

This specification relies on several other underlying specifications.

Web App Security

The following terms are defined in the Content Security Policy Level 3 specification: [CSP3]

• Should block navigation response

DOM

The following terms are defined in the Document Object Model specification: [DOM]

• Attribute
• context object
• compareDocumentPosition
• Document element
• Document
• DOCUMENT_POSITION_DISCONNECTED (1)
• Document type
• Document URL
• Element
• Equals
• Event
• Fire an event
• Get an attribute by name
• getAttribute
• getElementsByTagName
• hasAttribute
• HTMLCollection
• isTrusted
• Node
• NodeList
• Node Length
• ownerDocument
• querySelector
• querySelectorAll
• tagName
• Text content
• Text node

The following attributes are defined in the DOM Parsing and Serialisation specification: [DOM-PARSING]

• innerHTML IDL attribute
• outerHTML IDL attribute
• serializeToString

The following attributes are defined in the UI Events specification: [UI-EVENTS]

• Activation trigger
• click event
• Keyboard event
• Keyboard event order
• keyDown event
• keyPress event
• keyUp event
• mouseDown event
• Mouse event
• Mouse event order
• mouseMove event
• mouseOver event
• mouseUp event

The following attributes are defined in the UI Events Code specification: [UIEVENTS-CODE]

• Keyboard event code tables

The following attributes are defined in the UI Events Code specification: [UIEVENTS-KEY]

• Keyboard modifier keys

ECMAScript

The following terms are defined in the ECMAScript Language Specification: [ECMA-262]

• Create a function object
• Directive prologue
• Early error
• FunctionBody
• Function
• Global environment
• Own property
• parseFloat
• Use strict directive

This specification also presumes that you are able to call some of the internal methods from the ECMAScript Language Specification:

• [[Call]]
• [[Class]]
• [[GetOwnProperty]]
• [[GetProperty]]
• Index of
• [[Put]]
• Substring

The ECMAScript Language Specification also defines the following types, values, and operations that are used throughout this specification:

• Array
• Boolean type
• List
• Null
• Number
• Object
• [[Parse]]
• String
• [[Stringify]]
• ToInteger
• Undefined

Fetch

The following terms are defined in the WHATWG Fetch specification: [FETCH]

• Body
• Header
• Header Name
• Header Value
• Method
• Response
• Request
• Set Header
• HTTP Status
• Status message

Fullscreen

The following terms are defined in the WHATWG Fullscreen specification: [FULLSCREEN]

• Fullscreen element
• Fullscreen an element
• Fullscreen is supported
• fully exit fullscreen
• unfullscreen a document

HTML

The following terms are defined in the HTML specification: [HTML]

• 2D context creation algorithm
• A browsing context is discarded
• Active document
• Active element being the activeElement attribute on Document
• A serialization of the bitmap as a file
• Associated window
• body element
• Boolean attribute
• Browsing context
• Button state
• Buttons
• Canvas context mode
• color state
• multiple attribute
• Mutable
• change event
• Checkbox state
• Checkedness
• Child browsing context
• Close a browsing context
• Code entry-point
• Cookie-averse Document object
• Current entry
• Disabled
• Document address
• Document readiness
• Document title
• Element contexts
• Enumerated attribute
• Environment settings object
• Event loop
• File state
• File upload state
• Focusing steps
• Focusable area
• [[GetOwnProperty]] of a Window object
• Getting innerText
• Hidden state
• Image Button state
• In parallel
• input event applies
• input event
• Selected Files
• Joint session history
• Mature navigation.
• Missing value default state
• Navigate
• Navigator object
• Nested browsing context
• Origin-clean
• An overridden reload
• Parent browsing context
• HTML Pause
• Prompt to unload a document
• Radio Button state
• Refresh state pragma directive
• Reset algorithm
• Reset Button state
• Resettable element
• Script execution environment
• Script
• Selectedness
• Session history
• setSelectionRange
• Settings object
• Simple dialogs
• Submit Button state
• Suffering from bad input
• Submittable elements
• Top-level browsing context
• Traverse the history by a delta
• Traverse the history
• Tree order
• unfocusing steps
• User prompt
• value attribute
• Value

The HTML specification also defines a number of elements which this specification has special-cased behavior for:

• a element
• area element
• frame element
• iframe element
• canvas element
• datalist element
• html element
• input element
• map element
• optgroup element
• option element
• select element
• textarea element

The following types are also defined in the HTML specification, and referenced here:

• canvas’s height attribute
• canvas’ width attribute
• Window object
• WindowProxy exotic object
• readOnly attribute
• type attribute
• window.confirm
• window.alert
• window.print
• window.prompt

The HTML Editing APIs specification defines the following terms: [EDITING]

• Content editable

The following events are also defined in the HTML specification:

• beforeunload
• DOMContentLoaded
• load
• pageHide
• pageShow

The “data” URL scheme specification defines the following terms: [RFC2397]

• data: URL

HTTP and related specifications

To be HTTP compliant, it is supposed that the implementation supports the relevant subsets of [ RFC7230], [RFC7231], [RFC7232], [RFC7234], and [RFC7235].

The following terms are defined in the Cookie specification: [RFC6265]

• Compute cookie-string
• Cookie
• Cookie store
• Receives a cookie

The following terms are defined in the Hypertext Transfer Protocol (HTTP) Status Code Registry:

• Status code registry

The following terms are defined in the Netscape Navigator Proxy Auto-Config File Format:

• Proxy autoconfiguration

The specification uses URI Templates. [URI-TEMPLATE]

Infra

The following terms are defined in the Infra standard: [INFRA]

• ASCII lower alpha
• ASCII lowercase

Page Visibility

The following terms are defined in the Page Visibility Specification [PAGE-VISIBILITY]

• Document hidden attribute

Selenium

The following functions are defined within the Selenium project, at revision 1721e627e3b5ab90a06e82df1b088a33a8d11c20.

• bot.dom.getVisibleText
• bot.dom.isShown

Styling

The following terms are defined in the CSS Values and Units Module Level 3 specification: [CSS3-VALUES]

• CSS reference pixels

The following properties are defined in the CSS Basic Box Model Level 3 specification: [CSS3-BOX]

• The visibility property

The following terms are defined in the CSS Device Adaptation Module Level 1 specification: [CSS-DEVICE-ADAPT]

• Initial viewport, sometimes here referred to as the viewport.

The following properties are defined in the CSS Display Module Level 3 specification: [CSS3-DISPLAY]

• The display property

The following terms are defined in the Geometry Interfaces Module Level 1 specification: [GEOMETRY-1]

• DOMRect
• Rectangle
• Rectangle height dimension
• Rectangle width dimension
• Rectangle x coordinate
• Rectangle y coordinate

The following terms are defined in the CSS Cascading and Inheritance Level 4 specification: [CSS-CASCADE-4]

• Computed value

The following terms are defined in the CSS Object Model: [CSSOM]:

• Resolved value

The following functions are defined in the CSSOM View Module: [CSSOM-VIEW]:

• getBoundingClientRect
• Element from point as elementFromPoint()
• Elements from point as elementsFromPoint()
• getClientRects
• innerHeight
• innerWidth
• moveTo(x, y)
• offsetLeft
• offsetParent
• offsetTop
• screenX
• screenY
• scrollX
• scrollY
• scrollIntoView
• ScrollIntoViewOptions

SOCKS Proxy and related specification:

To be SOCKS Proxy and SOCKS authentication compliant, it is supposed that the implementation supports the relevant subsets of [ RFC1928] and [RFC1929].

Unicode

The following terms are defined in the standard: [Unicode]

• Code Point
• Extended grapheme cluster

Unicode Standard Annex #29

The following terms are defined in the standard: [UAX29]

• Grapheme cluster boundaries

Unicode Standard Annex #44

The following terms are defined in the standard: [UAX44]

• Unicode character property

URLs

The following terms are defined in the WHATWG URL standard: [URL]

• Absolute URL
• Absolute URL with fragment
• Domain
• Host
• Is special
• Local scheme
• Path-absolute URL
• Path
• Port
• URL
• URL serializer

Web IDL

The IDL fragments in this specification must be interpreted as required for conforming IDL fragments, as described in the Web IDL specification. [WEBIDL]

• DOMException
• Sequence
• Supported property indices
• SyntaxError

Promises Guide

The following terms are defined in the Promises Guide. [PROMISES-GUIDE]

• A new promise
• Promise-calling
• reject
• resolve

XML Namespaces

The following terms are defined in the Namespaces in XML [XML-NAMES]

• qualified element name

XPATH

The following terms are defined in the Document Object Model XPath standard [XPATH]

• evaluate
• XPathException

2.1 Compatibility

This specification is derived from the popular Selenium WebDriver browser automation framework. Selenium is a long-lived project, and due to its age and breadth of use it has a wide range of expected functionality. This specification uses these expectations to inform its design. Where improvements or clarifications have been made, they have been made with care to allow existing users Selenium WebDriver to avoid unexpected breakages.

2.2 Simplicity

The largest intended group of users of this specification are software developers and testers writing automated tests and other tooling, such as monitoring or load testing, that relies on automating a browser. As such, care has been taken to provide commands that simplify common tasks such as typing into and clicking elements.

2.3 Extensions

WebDriver aims to allow other standards to provide extensions to support new functionality, and to allow conformance tests that cannot be implemented entirely in ECMAScript to be written in a vendor-neutral way.

6.1 Algorithms

Various parts of this specification are written in terms of step-by-step algorithms. The details of these algorithms do not have any normative significance; implementations are free to adopt any implementation strategy that produces equivalent output to the specification. In particular, algorithms in this document are optimised for readability rather than performance.

Where algorithms that return values are fallible, they are written in terms of returning either success or error. A success value has an associated data field which encapsulates the value returned, whereas an error response has an associated error code.

When calling a fallible algorithm, the construct “Let result be the result of trying to call algorithm” is equivalent to

1. Let temp be the result of calling algorithm.

2. If temp is an error return temp, otherwise let result be temp’s data field.

The result of getting a property with name from an Object is defined as the result of calling the [[GetOwnProperty]] internal method of with property name name.

The result of setting a property with name and value to an Object is defined as calling the [[Put]] internal method with name name and value value.

The result of JSON serialization with object of type JSON Object and calling the [[Stringify]] function with argument object.

The result of JSON deserialization with text is defined as the result of calling the [[Parse]] function with text.

6.2 Commands

The WebDriver protocol is organised into commands. Each HTTP request with a method and template defined in this specification represents a single command, and therefore each command produces a single HTTP response. In response to a command, a remote end will run a series of actions against the browser.

Each command defined in this specification has an associated list of remote end steps. This provides the sequence of actions that a remote end takes when it receives a particular command.

6.3 Processing Model

The remote end is an HTTP server reading requests from the client and writing responses, typically over a TCP socket. For the purposes of this specification we model the data transmission between a particular local end and remote end with a connection to which the remote end may write bytes and read bytes. However the exact details of how this connection works and how it is established are out of scope.

After such a connection has been established, a remote end MUST run the following steps:

1. Read bytes from the connection until a complete HTTP request can be constructed from the data. Let request be a request constructed from the received data, according to the requirements of [RFC7230].

2. Let request match be the result of the algorithm to match a request with request’s method and URL as arguments.

3. If request match is of type error, send an error with request match’s error code and jump to step 1.

   Otherwise, let command and url variables be request match’s data.

4. Let session id be the corresponding variable from url variables.

5. If command is not New Session:

   1. If session id is not equal to the ID of any session in the list of active sessions, send an error with error code invalid session id, then jump to step 1 in this overall algorithm.

      Otherwise, let the current session be the session with ID session id.

6. If request’s method is POST:

   1. Let parse result be the result of parsing as JSON with request’s body as the argument.

   2. If parse result is an error or if it is a success but its associated data is not an Object, send an error with error code invalid argument and jump back to step 1 in this overall algorithm.

      Otherwise, let parameters be parse result’s data.

   Otherwise, let parameters be null.

7. Wait for navigation to complete. If this returns an error return its value and jump to step 1 in this overall algorithm, otherwise continue.

8. Let response result be the return value obtained by running the remote end steps for command with url variables as arguments.

9. If response result is an error, send an error with error code equal to response result’s error code and jump back to step 1 in this overall algorithm.

   Otherwise, if response result is a success, let response data be response result’s data.

10. Send a response with status 200 and response data.

11. Jump to step 1.

When required to send an error, with error code, a remote end must run the following steps:

1. Let http status and name be the error response data for error code.

2. Let message be an implementation-defined string containing a human-readable description of the reason for the error.

3. Let stacktrace be an implementation-defined string containing a stack trace report of the active stack frames at the time when the error occurred.

   Let data be a new JSON Object initialised with the following properties:

   error

   name

   message

   message

   stacktrace

   stacktrace

4. Send a response with status and data as arguments.

When required to send a response, with arguments status and data, a remote end must run the following steps:

1. Let response be a new response.

2. Set response’s HTTP status to status, and status message to the string corresponding to the description of status in the status code registry.

3. Set the response’s header with name and value with the following values:

   Content-Type

   "application/json; charset=utf-8"

   Cache-Control

   "no-cache"

4. Let response’s body be a JSON Object with a key value set to the JSON serialization of data.

5. Let response bytes be the byte sequence resulting from serializing response according to the rules in [RFC7230].

6. Write response bytes to the connection.

6.4 Routing Requests

Request routing is the process of going from a HTTP request to the series of steps needed to implement the command represented by that request.

A remote end has an associated URL prefix, which is used as a prefix on all WebDriver-defined URLs on that remote end. This must either be undefined or an path-absolute URL.

In order to match a request given a method and URL, the following steps must be taken:

1. Let endpoints be a list containing each row in the table of endpoints.

2. Remove each entry from endpoints for which the concatenation of the URL prefix and the entry’s URI template does not match URL’s path.

3. If there are no entries in endpoints, return error with error code unknown command.

4. Remove each entry in endpoints for which the method column is not an exact case-sensitive match for method.

5. If there are no entries in endpoints, return error with error code unknown method.

6. There is now exactly one entry in endpoints; let entry be this entry.

7. Let parameters be the result of extracting the variables from URL using entry’s URI template.

8. Let command be entry’s command.

9. Return success with data command and parameters.

6.5 List of Endpoints

The following table of endpoints lists the method and URI template for each endpoint node command.

6.6 Handling Errors

Errors are represented in the WebDriver protocol by an HTTP response with an HTTP status in the 4xx or 5xx range, and a JSON body containing details of the error. This JSON body has three fields: error, containing a string indicating the error type; message, containing an implementation-defined string with a human readable description of the kind of error that occurred; and stacktrace, containing an implementation-defined string with a stack trace report of the active stack frames at the time when the error occurred.

The following table lists each error code, its associated HTTP status, JSON error code, and a non-normative description of the error. The error response data for a particular error code is the values of the HTTP Status and JSON Error Code columns for the row corresponding to that error code.

6.7 Protocol Extensions

The protocol is designed to allow extension to meet vendor-specific needs. Commands that are specific to a user agent are called extension commands and behave no differently than other commands; each has a dedicated HTTP endpoint and a set of remote end steps.

Each extension command has an associated extension command name that is an ASCII lower alpha string, and which should bear some resemblance to what the command performs. The name is used to form an extension command’s URL.

The extension command’s extension command URL is a URL composed of the extension command prefix, followed by "/", and the extension command’s name. The extension command URL, along with the HTTP method and extension command, is added to the table of endpoints and thus follows the same rules for request routing as that of other built-in commands.

An extension command prefix is an ASCII lower alpha string that forms a URL path part, separating extension commands from other commands in order to avoid potential resource conflicts with other implementations. It is suggested that vendors use their vendor prefixes without additional characters as outlined in [CSS21], notably in section 4.1.2.2 on vendor keywords, as the name for this path element, and include a vendor-chosen UA identifier.

Remote ends may also introduce extension capabilities that are extra capabilities used to provide configuration or fulfill other vendor-specific needs. Extension capabilities’ key must contain a ":" (colon) character, denoting an implementation specific namespace. The value can be arbitrary JSON types.

As with extension commands, it is suggested that the key used to denote the extension capability namespace is based on the vendor keywords listed in [CSS21] and precedes the first ":" character in the string.

7.1 Proxy

The proxy configuration capability is a JSON Object nested within the primary capabilities. Implementations may define additional proxy configuration options, but they must not alter the semantics of those listed below.

The remote end steps to deserialize as a proxy argument parameter are:

1. If parameter is not a JSON Object return an error with error code invalid argument.

2. Let proxy be a new, empty proxy configuration object.

3. For each enumerable own property in parameter run the following substeps:

   1. Let key be the name of the property.

   2. Let value be the result of getting a property named name from parameter.

   3. Let key be the result of lowercasing key.

   4. If there is no matching key for key in the proxy configuration table return an error with error code invalid argument.

   5. If value is not one of the valid values for that key, return an error with error code invalid argument.

   6. Set a property key to value on proxy.

A proxy configuration object is a JSON Object where each of its own properties matching keys in the proxy configuration meets the validity criteria for that key.

7.2 Processing Capabilities

To process capabilities with argument parameters, the endpoint node must take the following steps:

1. Let capabilities request be the result of getting a property named "capabilities" from parameters.

   1. If capabilities request is not a JSON object, return error with error code invalid argument.

2. Let required capabilities be the result of getting a property named "alwaysMatch" from capabilities request.

   1. If required capabilities is undefined, set the value to an empty JSON Object.

   2. Let required capabilities be the result of trying to validate capabilities with argument required capabilities.

3. Let all first match capabilities be the result of getting a property named "firstMatch" from capabilities request.

   1. If all first match capabilities is undefined, set the value to a JSON List with a single entry of an empty JSON Object.

   2. If all first match capabilities is not a JSON List, return error with error code invalid argument.

4. Let validated first match capabilities be an empty JSON List.

5. For each first match capabilities corresponding to an indexed property in all first match capabilities:

   1. Let validated capabilities be the result of trying to validate capabilities with argument first match capabilities.

   2. Append validated capabilities to validated first match capabilities.

6. For each first match capabilities corresponding to an indexed property in validated first match capabilities:

   1. Let merged capabilities be the result of trying to merge capabilities with required capabilities and first match capabilities as arguments.

   2. Let matched capabilities be the result of trying to match capabilities with merged capabilities as an argument.

   3. If matched capabilities is not null return matched capabilities.

7. Return success with data null.

When required to validate capabilities with argument capability:

1. If capability is not a JSON Object return an error with error code invalid argument.

2. Let result be an empty JSON Object.

3. For each enumerable own property in capability, run the following substeps:

   1. Let name be the name of the property.

   2. Let value be the result of getting a property named name from capability.

   3. Run the substeps of the first matching condition:

      value is null

      Let deserialized be set to null.

      name equals "acceptInsecureCerts"

      If value is not a boolean return an error with error code invalid argument. Otherwise, let deserialized be set to value

      name equals "browserName"

      name equals "browserVersion"

      name equals "platformName"

      If value is not a string return an error with error code invalid argument. Otherwise, let deserialized be set to value.

      name equals "pageLoadStrategy"

      Let deserialized be the result of trying to deserialize as a page load strategy with argument value.

      name equals "proxy"

      Let deserialized be the result of trying to deserialize as a proxy with argument value.

      name equals "timeouts"

      Let deserialized be the result of trying to deserialize as a timeout with argument value.

      name equals "unhandledPromptBehavior"

      Let deserialized be the result of trying to deserialize as an unhandled prompt behavior with argument value.

      name is the key of an extension capability

      Let deserialized be the result of trying to deserialize value in an implementation-specific way.

      The remote end is an endpoint node

      Return an error with error code invalid argument.

   4. If deserialized is not null, set a property on result with name name and value deserialized.

4. Return success with data result.

When merging capabilities with JSON Object arguments primary and secondary, an endpoint node must take the following steps:

1. Let result be a new JSON Object.

2. For each enumerable own property in primary, run the following substeps:

   1. Let name be the the name of the property.

   2. Let value be the the result of getting a property named name from primary.

   3. Set a property on result with name name and value value.

3. If secondary is undefined, return result.

4. For each enumerable own property in secondary, run the following substeps:

   1. Let name be the the name of the property.

   2. Let value be the the result of getting a property named name from secondary.

   3. Let primary value be the result of getting a property named name from primary.

   4. If primary value is not undefined return an error with error code invalid argument.

   5. Set a property on result with name name and value value.

5. Return result.

When matching capabilities with JSON Object argument capabilities, an endpoint node must take the following steps:

1. Let matched capabilities be a JSON Object with the following entries:

   "browserName"

   Lowercase name of the user agent as a string.

   "browserVersion"

   The user agent version, as a string.

   "platformName"

   Lowercase name of the current platform as a string.

   "acceptInsecureCerts"

   Boolean initially set to false, indicating the session will not implicitly trust untrusted or self-signed TLS certificates on navigation.

   "setWindowRect"

   Boolean indicating whether the remote end supports all of the commands in Resizing and Positioning Windows.

2. Optionally add extension capabilities as entries to matched capabilities. The values of these may be ellided, and there is no requirement that all extension capabilities be added.

   Note

3. For each name and value corresponding to capability's own properties:

   1. Run the substeps of the first matching name:

      "browserName"

      If value is not a string equal to the "browserName" entry in matched capabilities, return success with data null.

      Note

      There is a chance the remote end will need to start a browser process to correctly determine the browserName. Lightweight checks are preferred before this is done.

      "browserVersion"

      Compare value to the "browserVersion" entry in matched capabilities using an implementation-defined comparison algorithm. The comparison is to accept a value that places constraints on the version using the "<", "<=", ">", and ">=" operators.

      If the two values do not match, return success with data null.

      Note

      Version comparison is left as an implementation detail since each user agent will likely have conflicting methods of encoding the user agent version, and standardizing these schemes is beyond the scope of this standard.

      Note

      There is a chance the remote end will need to start a browser process to correctly determine the browserVersion. Lightweight checks are preferred before this is done.

      "platformName"

      If value is not a string equal to the "platformName" entry in matched capabilities, return success with data null.

      Note

      The following platform names are in common usage with well-understood semantics and are to be treated as valid platformNames for the following Operating Systems:

      Platform	Operating System
      linux	Any OS based upon the Linux kernel and X Windows.
      mac	Any version of Apple's OS X.
      windows	Any version of Microsoft's Windows, including desktop and mobile versions.

      This list is not exhaustive.

      "acceptInsecureCerts"

      If value is true and the endpoint node does not support insecure TLS certificates, return success with data null.

      Note

      If the endpoint node does not support insecure TLS certificates and this is the reason no match is ultimately made, it is useful to provide this information to the local end.

      "proxy"

      If the endpoint node does not allow the proxy it uses to be configured, or if the proxy configuration defined in value is not one that passes the endpoint node's implementation-specific validity checks, return success with data null.

      Note

      A local end would only send this capability if it expected it to be honored and the configured proxy used. The intent is that if this is not possible a new session will not be established.

      Otherwise

      If name is the key of an extension capability,

      let value be the result of trying implementation-specific steps to match on name with value. If the match is not successful, return success with data null.

   2. Set a property on matched capability with name name and value value.

4. Return success with data matched capabilities.

8.1 New Session

The New Session command creates a new WebDriver session with the endpoint node. If the creation fails, a session not created error is returned.

If the remote end is an intermediary node, it MAY use the result of the capabilities processing algorithm to route the new session request to the appropriate endpoint node. An intermediary node MAY also define custom capabilities to assist in this process, however, these capabilities MUST NOT be forwarded to the endpoint node.

If the intermediary node requires additional information unrelated to user agent features, it is RECOMMENDED that this information be passed as top-level parameters, and not as part of the requested capabilities. An intermediary node MAY forward custom, top-level parameters (i.e. non-capabilities) to subsequent remote end nodes.

The remote end steps are:

1. If the maximum active sessions is equal to the length of the list of active sessions, return error with error code session not created.

2. If the remote end is an intermediary node, take implementation-defined steps that either result in returning an error with error code session not created, or in returning a success with data that is isomorphic to that returned by remote ends according to the rest of this algorithm. If an error is not returned, the intermediary node must retain a reference to the session created on the upstream node as the associated session such that commands may be forwarded to this associated session on subsequent commands.

   Note

   How this is done is entirely up to the implementation, but typically the sessionId, and URL and URL prefix of the upstream remote end will need to be tracked.

3. If the maximum active sessions is equal to the length of the list of active sessions, return error with error code session not created.

4. Let capabilities be the result of trying to process capabilities with parameters as an argument.

5. If capabilities's is null, return error with error code session not created.

6. Let session id be a UUID.

7. Let session be a new session with the session ID of session id.

8. Set the current session to session.

9. Append session to active sessions.

10. Let body be a JSON Object initialised with:

    sessionId

    session id

    capabilities

    capabilities

11. Initialize the following from capabilities:

    1. Let strategy be the result of getting property " pageLoadStrategy" from capabilities.

    2. If strategy is a string, set the current session’s page loading strategy to strategy. Otherwise, set the page loading strategy to normal and set a property of capabilities with name " pageLoadStrategy" and value "normal".

    3. Let proxy be the result of getting property " proxy" from capabilities and run the substeps of the first matching statement:

       proxy is a proxy configuration object

       Take implementation-defined steps to set the user agent proxy using the extracted proxy configuration. If the defined proxy cannot be configured return error with error code session not created.

       Otherwise

       Set a property of capabilities with name " proxy" and a value that is a new JSON Object.

    4. Let timeouts be the result of getting property " timeouts" from capabilities.

    5. If timeouts is a session timeouts configuration object:

       1. If timeouts has a numeric property with key "implicit", set the current session’s session implicit wait timeout to the value of property "implicit". Otherwise, set the session implicit wait timeout to 0 (zero) milliseconds.

       2. If timeouts has a numeric property with key "pageLoad", set the current session’s session page load timeout to the value of property "pageLoad". Otherwise, set the session page load timeout to 300,000 milliseconds.

       3. If timeouts has a numeric property with key "script", set the current session’s session script timeout to the value of property "script". Otherwise, set the session script timeout to 30,000 milliseconds.

    6. Let configured timeouts be a new JSON Object.

    7. Set a property on configured timeouts with name " implicit" and value equal to the current session’s session implicit wait timeout.

    8. Set a property on configured timeouts with name " pageLoad" and value equal to the current session’s session page load timeout.

    9. Set a property on configured timeouts with name " script" and value equal to the current session’s session script timeout.

    10. Set a property on capabilties with name " timeouts" and value configured timeouts.

    11. Apply changes to the user agent for any implementation-defined capabilities selected during the capabilities processing step.

12. Set the webdriver-active flag to true.

13. Return success with data body.

8.2 Delete Session

The Delete Session command closes any top-level browsing contexts associated with the current session, terminates the connection, and finally closes the current session.

The remote end steps are:

1. Try to close the session.

2. Return success with data null.

8.3 Status

The Status command returns information about whether a remote end is in a state in which it can create new sessions and can additionally include arbitrary meta information that is specific to the implementation.

The readiness state is represented by the ready property of the body, which is false if an attempt to create a session at the current time would fail. However, the value true does not guarantee that a New Session command will succeed.

Implementations may optionally include additional meta information as part of the body, but the top-level properties ready and message are reserved and must not be overwritten.

The remote end steps are:

1. Let body be a new JSON Object with the following properties:

   "ready"

   The remote end’s readiness state.

   "message"

   An implementation-defined string explaining the remote end’s readiness state.

2. Return success with data body.

8.4 Get Timeouts

The Get Timeouts command gets timeout durations associated with the current session.

The remote end steps are:

1. Let body be a new JSON Object with the following properties:

   "script"

   session script timeout

   "pageLoad"

   session page load timeout

   "implicit"

   session implicit wait timeout

2. Return success with data body.

8.5 Set Timeouts

The Set Timeouts command sets timeout durations associated with the current session. The timeouts that can be controlled are listed in the table of session timeouts below.

The following table of session timeouts enumerates the different timeout types that may be set. The keywords given in the first column maps to the timeout type given in the second.

A session timeouts configuration is a JSON Object. It consists of the properties named after the keys in the table of session timeouts and may include implementation-specific timeouts.

The steps to deserialize as a timeout with argument parameters are:

1. If parameters is not a JSON Object, return error with error code invalid argument.

2. For each enumerable own property in parameters, run the following substeps:

   1. Let name be the name of the property.

   2. Let value be the result of getting a property named name from parameters.

   3. Find the timeout type from the table of session timeouts by looking it up by its keyword key.

      If no keyword matches key, return error with error code invalid argument.

   4. If value is not an integer, or it is less than 0 or greater than 2⁶⁴ – 1, return error with error code invalid argument.

3. Return success with data parameters.

The remote end steps are:

1. Let parameters be the result of trying to deserialize as a timeout parameters.

2. For each enumerable own property in parameters:

   1. Let key be the name of the property.

   2. Let value be the result of getting a property named name from parameters.

   3. Find the timeout type from the table of session timeouts by looking it up by its keyword key.

   4. Set timeout type’s value.

3. Return success with data null.

9.1 Go

The Go command is used to cause the user agent to navigate the current top-level browsing context a new location.

If the session is not in a secure TLS state, no certificate errors that would normally cause the user agent to abort and show a security warning are to be hinder navigation to the requested address.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. If the url property is missing from the parameters argument or it is not a string, return error with error code invalid argument.

4. Let url be the result of getting a property named url from the parameters argument.

5. If url is not an absolute URL or is not an absolute URL with fragment or not a local scheme, return error with error code invalid argument.

6. Let current URL be the current top-level browsing context’s active document’s document URL.

7. If current URL and url do not have the same absolute URL:

   1. If timer has not been started, start a timer. If this algorithm has not completed before timer reaches the session's session page load timeout in milliseconds, return an error with error code timeout.

8. Navigate the current top-level browsing context to url.

9. If url is special except for file and current URL and URL do not have the same absolute URL :

   1. Run the post-navigation checks and return its value if it is an error.

   2. Try to wait for navigation to complete.

10. Set the current browsing context to the current top-level browsing context.

11. If the current top-level browsing context contains a refresh state pragma directive of time 1 second or less, wait until the refresh timeout has elapsed, a new navigate has begun, and return to the first step of this algorithm.

12. Return success with data null.

9.2 Get Current URL

The Get Current URL command returns the URL of the current top-level browsing context.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let url be the serialization of the current top-level browsing context’s active document’s document URL.

4. Return success with data url.

9.3 Back

The Back command causes the browser to traverse one step backward in the joint session history of the current top-level browsing context. This is equivalent to pressing the back button in the browser chrome or calling window.history.back.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Traverse the history by a delta –1 for the current browsing context.

4. If the previous step completed results in a pageHide event firing, wait until pageShow event fires or for the session page load timeout milliseconds to pass, whichever occurs sooner.

5. If the previous step completed by the session page load timeout being reached, and user prompts have been handled, return error with error code timeout.

6. Return success with data null.

9.4 Forward

The Forward command causes the browser to traverse one step forwards in the joint session history of the current top-level browsing context.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Traverse the history by a delta 1 for the current browsing context.

4. If the previous step completed results in a pageHide event firing, wait until pageShow event fires or for the session page load timeout milliseconds to pass, whichever occurs sooner.

5. If the previous step completed by the session page load timeout being reached, and user prompts have been handled, return error with error code timeout.

6. Return success with data null.

9.5 Refresh

The Refresh command causes the browser to reload the page in in current top-level browsing context.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Initiate an overridden reload of the current top-level browsing context's active document.

4. Run the post-navigation checks and return its value if it is an error.

5. Try to wait for navigation to complete.

6. Set the current browsing context to the current top-level browsing context.

7. Return success with data null.

9.6 Get Title

The Get Title command returns the document title of the current top-level browsing context, equivalent to calling document.title.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let title be the initial value of the title IDL attribute of the current top-level browsing context's active document.

4. Return success with data title.

10.1 Get Window Handle

The Get Window Handle command returns the window handle for the current top-level browsing context. It can be used as an argument to Switch To Window.

The remote end steps are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Return success with data being the window handle associated with the current top-level browsing context.

10.2 Close Window

The remote end steps for the Close Window command are:

1. If the current top-level browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Close the current top-level browsing context.

4. If there are no more open top-level browsing contexts, then try to close the session.

5. Return the result of running the remote end steps for the Get Window Handles command.

10.3 Switch To Window

The Switch To Window command is used to select the current top-level browsing context for the current session, i.e. the one that will be used for processing commands.

The remote end steps are:

1. If there is an active user prompt, that due to the uniqueness of the user agent prevents the focussing of another top-level browsing context, return error with error code unsupported operation.

2. Let handle be the result of getting a property named "handle" from the parameters argument.

3. If handle is equal to the associated window handle for some top-level browsing context in the current session, set the session’s current browsing context to that browsing context, and return success with data null.

   Otherwise, return error with error code no such window.

10.4 Get Window Handles

The Get Window Handles command returns a list of window handles for every open top-level browsing context. The order in which the window handles are returned is arbitrary.

The remote end steps are:

1. Let handles be a JSON List.

2. For each top-level browsing context in the remote end, push the associated window handle onto handles.

3. Return success with data handles.

10.5 Switch To Frame

The Switch To Frame command is used to select the current top-level browsing context or a child browsing context of the current browsing context to use as the current browsing context for subsequent commands.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let id be the result of getting a property named "id" from the parameters argument.

4. Run the substeps of the first matching condition:

   id is null

   1. Set the current browsing context to the current top-level browsing context.

   id is a Number object

   1. If id is less than 0 or greater than 2¹⁶ – 1, return error with error code no such frame.

   2. Let window be the associated window of the current browsing context’s active document.

   3. If id is not a supported property index of window, return error with error code no such frame.

   4. Let child window be the WindowProxy object obtained by calling [[GetOwnProperty]] of a Window object window with argument id.

   5. Set the current browsing context to new window’s browsing context.

   id represents a web element

   1. Let element be the result of trying to get a known element by web element reference id.

   2. If element is stale, return error with error code stale element reference.

   3. If element is not a frame or iframe element, return error with error code no such frame.

   4. Set the current browsing context to element’s nested browsing context.

   Otherwise

   1. Return error with error code no such frame.

5. Return success with data null.

10.6 Switch To Parent Frame

The Switch to Parent Frame command sets the current browsing context for future commands to the parent of the current browsing context.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. If the current browsing context is not equal to the current top-level browsing context, set the current browsing context to the parent browsing context of the current browsing context.

4. Return success with data null.

10.7 Resizing and Positioning Windows

WebDriver provides commands for interacting with the operating system window containing the current top-level browsing context. Because different operating system’s window managers provide different abilities, not all of the commands in this section can be supported by all remote ends. Support for these commands is determined by the window dimensioning/positioning capability. Where a command is not supported, an unsupported operation error is returned.

A top-level browsing context’s window rect is defined as a dictionary of the screenX, screenY, width and height attributes of the WindowProxy. Its JSON representation is the following:

x

WindowProxy’s screenX attribute.

y

WindowProxy’s screenY attribute.

width

Width of the top-level browsing context’s outer dimensions, including any browser chrome and externally drawn window decorations in CSS reference pixels.

height

Height of the top-level browsing context’s outer dimensions, including any browser chrome and externally drawn window decorations in CSS reference pixels.

In some user agents the operating system’s window dimensions including decorations, are provided by the proprietary window.outerWidth and window.outerHeight [DOM] properties.

11.1 Element Interactability

In order to determine if an element can be interacted with using pointer actions, WebDriver performs hit-testing to find if the interaction will be able to reach the requested element.

An interactable element is an element which is either pointer-interactable or keyboard-interactable.

A pointer-interactable element is defined to be the first element, defined by the paint order found at the center point of its rectangle that is inside the viewport, excluding the size of any rendered scrollbars.

A keyboard-interactable element is defined to be any element that has a focusable area, or is the body element. In the case of the body element all keyboard interactions must be targeted to its ownerDocument.

An element’s in-view center point is the origin position of the rectangle that is the intersection between the element’s first DOM client rectangle and the initial viewport. Given an element that is known to be in view, it can be calculated this way:

1. Let rectangle be the first element of the DOMRect sequence returned by calling getClientRects on element.

2. Let left be (max(0, min(x coordinate, x coordinate + width dimension))).

3. Let right be (min(innerWidth, max(x coordinate, x coordinate + width dimension))).

4. Let top be (max(0, min(y coordinate, y coordinate + width dimension))).

5. Let bottom be (min(innerHeight, max(y coordinate, y coordinate + height dimension))).

6. Let x be (0.5 × (left + right).

7. Let y be (0.5 × (top + bottom).

8. Return x and y as a pair.

An element is in view if it is a member of its own pointer-interactable paint tree.

An element is obscured if it is not pointer-interactable and the first pointer-interactable element at its center point is not itself.

In order to produce a pointer-interactable paint tree from an element:

1. If element is not in the same tree as the current browsing context’s active document, return an empty sequence.

2. Let rectangles be the DOMRect sequence returned by calling element’s getClientRects.

3. If rectangles has the length of 0, return an empty sequence.

4. Let center point be the in-view center point of element given the first indexed element of rectangles.

5. Return the elements from point given the coordinates center point.

To get the first pointer-interactable element given a pointer-interactable paint tree, return with success the first element. Otherwise, if there are no such elements, return an error.

11.2 Get Active Element

Get Active Element returns the active element of the current browsing context’s document element.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let active element be the active element of the current browsing context’s document element.

4. Let active web element be the JSON Serialization of active element.

5. Return success with data active web element.

12.1 Locator Strategies

An element location strategy is an enumerated attribute deciding what technique should be used to search for elements in the current browsing context. The following table of location strategies lists the keywords and states defined for this attribute:

12.2 Find Element

The Find Element command is used to find an element in the current browsing context that can be used for future commands.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let start node be the current browsing context’s document element.

3. Let location strategy be the result of getting a property called "using".

4. If location strategy is not present as a keyword in the table of location strategies, return error with error code invalid argument.

5. Let selector be the result of getting a property called "value".

6. If selector is undefined, return error with error code invalid argument.

7. Let result be the result of Find with start node, location strategy, and selector.

8. If result is empty, return error with error code no such element. Otherwise, return the first element of result.

12.3 Find Elements

The Find Elements command is used to find elements in the current browsing context that can be used for future commands.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let start node be the current browsing context’s document element.

3. Let location strategy be the result of getting a property called "using".

4. If location strategy is not present as a keyword in the table of location strategies, return error with error code invalid argument.

5. Let selector be the result of getting a property called "value".

6. If selector is undefined, return error with error code invalid argument.

7. Return the result of Find with start node, location strategy, and selector.

12.4 Find Element From Element

The Find Element From Element command is used to find an element from a web element in the current browsing context that can be used for future commands.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let start node be the result of trying to get a known element with argument element id.

3. Let location strategy be the result of getting a property called "using".

4. If location strategy is not present as a keyword in the table of location strategies, return error with error code invalid argument.

5. Let selector be the result of getting a property called "value".

6. If selector is undefined, return error with error code invalid argument.

7. Let result be the value of calling Find with start node, location strategy, and selector.

8. If result is empty, return error with error code no such element. Otherwise, return the first element of result.

12.5 Find Elements From Element

The Find Elements From Element command is used to find elements from a web element in the current browsing context that can be used for future commands.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let start node be the result of trying to get a known element with argument element id.

3. Let location strategy be the result of getting a property called "using".

4. If location strategy is not present as a keyword in the table of location strategies, return error with error code invalid argument.

5. Let selector be the result of getting a property called "value".

6. If selector is undefined, return error with error code invalid argument.

7. Return the result of Find with start node, location strategy, and selector.

13.1 Is Element Selected

Is Element Selected determines if the referenced element is selected or not. This operation only makes sense on input elements of the Checkbox- and Radio Button states, or option elements.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. Let selected be the value corresponding to the first matching statement:

   element is an input element with a type attribute in the Checkbox- or Radio Button state

   The result of element’s checkedness.

   element is an option element

   The result of element’s selectedness.

   Otherwise

   False.

6. Return success with data selected.

13.2 Get Element Attribute

The Get Element Attribute command will return the attribute of a web element.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. If name is undefined, return error with error code invalid argument.

6. Let result be the result of the first matching condition:

   If name is a boolean attribute

   "true" (string) if the element has the attribute, otherwise null.

   Otherwise

   The result of getting an attribute by name name.

7. Return success with data result.

13.3 Get Element Property

The Get Element Property command will return the result of getting a property of an element.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. Let property be the result of calling the [[GetProperty]] internal method of element with property name name.

6. Let result be the value of property if not undefined, or null.

7. Return success with data result.

13.4 Get Element CSS Value

The Get Element CSS Value command retrieves the computed value of the given CSS property of the given web element.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. Let computed value be the computed value of parameter property name from element’s style declarations if the current browsing context’s document type is not "xml", else let it be "carview.php?tsp=".

6. Return success with data computed value.

13.5 Get Element Text

The Get Element Text command intends to return an element’s text “as rendered”. This is approximately equivalent to calling element.innerText. An element’s rendered text is also used for locating a elements by their link text and partial link text.

When processing text, whitespace is defined as characters from the Unicode Character Database ([UAX44]) with the Unicode character property "WSpace=Y".

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. Let rendered text be the result of performing implementation-specific steps that are exactly analogous to the result of a [[Call]] to bot.dom.getVisibleText, providing null as the this value, and element as the argument.

5. Return success with data rendered text.

13.6 Get Element Tag Name

The Get Element Tag Name command returns the qualified element name of the given web element.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. Let qualified name be the result of getting element’s tagName content attribute.

6. Return success with data qualified name.

13.7 Get Element Rect

The Get Element Rect command returns the dimensions and coordinates of the given web element. The returned value is a dictionary with the following members:

x

X axis position of the top-left corner of the web element relative to the current browsing context’s document element in CSS reference pixels.

y

Y axis position of the top-left corner of the web element relative to the current browsing context’s document element in CSS reference pixels.

height

Height of the web element’s bounding rectangle in CSS reference pixels.

width

Width of the web element’s bounding rectangle in CSS reference pixels.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If the element is stale, return error with error code stale element reference.

5. Calculate the absolute position of element and let it be coordinates.

6. Let rect be element’s bounding rectangle.

7. Let body be a new JSON Object initialised with:

   x

   The first value of coordinates.

   y

   The second value of coordinates.

   width

   Value of rect’s width dimension.

   height

   Value of rect’s height dimension.

8. Return success with data body.

13.8 Is Element Enabled

Is Element Enabled determines if the referenced element is enabled or not. This operation only makes sense on form controls.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Handle any user prompts and return its value if it is an error.

3. Let element be the result of trying to get a known element with argument element id.

4. If element is stale, return error with error code stale element reference.

5. Let enabled be a boolean initially set to true if the current browsing context’s document type is not "xml".

   Otherwise, let enabled to false and jump to the last step of this algorithm.

6. Set enabled to false if a form control is disabled.

7. Return success with data enabled.

14.1 Element Click

The Element Click command scrolls into view the element if it is not already pointer-interactable, and clicks its in-view center point. If the element’s center point is obscured by another element, an element click intercepted error is returned. If the element is outside the viewport, an element not interactable error is returned.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let element be the result of trying to get a known element by reference element id.

3. If the element is an input element in the file upload state return error with error code invalid argument.

4. Scroll into view the element’s container.

5. Wait in an implementation-specific way up to the session implicit wait timeout for the container to become in view.

6. If element’s container is still not in view, return error with error code element not interactable.

7. If element’s container is obscured by another element, return error with error code element click intercepted.

8. Matching on element:

   option element

   1. Let parent node be the element's container.

   2. Fire a mouseOver event at parent node.

   3. Fire a mouseMove event at parent node.

   4. Fire a mouseDown event at parent node.

   5. Run the focusing steps on parent node.

   6. Fire an input event at parent node.

   7. Let previous selectedness be equal to element selectedness.

   8. Set element’s selectedness state to true.

   9. If previous selectedness is false:

      1. Fire a change event at parent node.

   10. Fire a mouseUp event at parent node.

   11. Fire a click event at parent node.

   Otherwise

   Issue 3

   Run interaction steps on coordinate.

9. Wait until the user agent event loop has spun enough times to process the DOM events generated by the previous step.

10. If the click causes navigation:

    1. Run the post-navigation checks and return its value if it is an error.

    2. Try to wait for navigation to complete.

    Note that one may not know if a click causes navigation. It is safe to run the post-navigation checks and waiting for the navigation to complete even though navigation did not occur.

11. Return success with data null.

14.2 Element Clear

The Element Clear command scrolls into view an editable or resettable element and then attempts to clear its selected files or text content.

The remote end steps are:

1. If the current browsing context is no longer open, return error with error code no such window.

2. Let element be the result of trying to get a known element with argument element id.

3. If element is not editable and is not resettable return an error with error code invalid element state.

4. Scroll into view the element.

5. Wait in an implementation-specific way up to the session implicit wait timeout for element to become interactable.

6. If element is not interactable, return error with error code element not interactable.

7. If element is disabled, read only, or has pointer events disabled, return error with error code invalid element state.

8. If element is content editable follow the steps required to clear a content editable element. Otherwise, follow the steps required to clear a resettable element.

9. Return success with data null.

When required to clear a content editable element a remote end must run the following steps:

1. If element's innerHTML IDL attribute is an empty string do nothing and return.

2. Run the focusing steps for element.

3. Set element's innerHTML IDL attribute to an empty string.

4. Run the unfocusing steps for the element.

When required to clear a resettable element a remote end must run the following steps:

1. If element's value is an empty string do nothing and return.

2. Run the focusing steps for element.

3. Run element's reset algorithm.

4. Run the unfocusing steps for the element.

14.3 Element Send Keys

The Element Send Keys command scrolls into view the form control element and then sends the provided keys to the element. In case the element is not keyboard-interactable, an element not interactable error is returned.

The key input state used for input may be cleared mid-way through “typing” by sending the null key, which is U+E000 (NULL).

When required to clear the modifier key state with an argument of undo actions and keyboard a remote end must run the following steps:

1. If keyboard is not a key input source return error with error code invalid argument.

2. For each entry key in the lexically sorted keys of undo actions:

   1. Let action be the value of undo actions matching key entry key.

   2. If action is not an action object of type "key" and subtype "keyUp", return error with error code invalid argument.

   3. Dispatch a keyUp action with arguments action and keyboard’s key input state.

An extended grapheme cluster is typeable if it consists of a single unicode code point and the code is not undefined.

The shifted state for keyboard is the value of keyboard’s key input state’s shift property.

In order to dispatch the events for a typeable string with arguments text and keyboard, a remote end must for each char corresponding to an indexed property in text:

1. If char is a shifted character and the shifted state of keyboard is false, create a new action object with keyboard's id, "key", and "keyDown", and set its value property to U+E008 ("left shift"). Dispatch a keyDown action with this action object and keyboard's key input state.

2. If char is not a shifted character and the shifted state of keyboard is true, create a new action object with keyboard's id, "key", and "keyUp", and set its value property to U+E008 ("left shift"). Dispatch a keyUp action with this action object and keyboard's key input state.

3. Let keydown action be a new action object constructed with arguments keyboard's id, "key", and "keyDown".

4. Set the value property of keydown action to char

5. Dispatch a keyDown action with arguments keydown action and keyboard's key input state.

6. Let keyup action be a copy of keydown action with the subtype property changed to "keyUp".

7. Dispatch a keyUp action with arguments keyup action and keyboard's key input state.