WebDriver BiDi

When an algorithm algorithm running in parallel awaits a set of events events, and resume id:

1. Pause the execution of algorithm.

2. Assert: wait queue does not contain resume id.

3. Set wait queue[resume id] to (events, algorithm).

To resume given name, id and parameters:

1. If wait queue does not contain id, return.

2. Let (events, algorithm) be wait queue[id]

3. For each event in events:

   1. If event equals name:

      1. Remove id from wait queue.

      2. Resume running the steps in algorithm from the point at which they were paused, passing name and parameters as the result of the await.

         Should we have something like microtasks to ensure this runs before any other tasks on the event loop?

Command = {
  id: js-uint,
  CommandData,
  Extensible,
}

CommandData = (
  BrowserCommand //
  BrowsingContextCommand //
  InputCommand //
  NetworkCommand //
  ScriptCommand //
  SessionCommand //
  StorageCommand
)

EmptyParams = {
   Extensible
}

Message = (
  CommandResponse /
  ErrorResponse /
  Event
)

CommandResponse = {
  type: "success",
  id: js-uint,
  result: ResultData,
  Extensible
}

ErrorResponse = {
  type: "error",
  id: js-uint / null,
  error: ErrorCode,
  message: text,
  ? stacktrace: text,
  Extensible
}

ResultData = (
  BrowsingContextResult /
  EmptyResult /
  NetworkResult /
  ScriptResult /
  SessionResult /
  StorageResult
)

EmptyResult = {
  Extensible
}

Event = {
  type: "event",
  EventData,
  Extensible
}

EventData = (
  BrowsingContextEvent //
  LogEvent //
  NetworkEvent //
  ScriptEvent
)

Extensible = (*text => any)

js-int = -9007199254740991..9007199254740991
js-uint = 0..9007199254740991

The list of active BiDi sessions is given by:

1. Let BiDi sessions be a new list.

2. For each session in active sessions:

   1. If session is a BiDi session append session to BiDi sessions.

3. Return BiDi sessions.

ErrorCode = "invalid argument" /
            "invalid selector" /
            "invalid session id" /
            "move target out of bounds" /
            "no such alert" /
            "no such element" /
            "no such frame" /
            "no such handle" /
            "no such history entry" /
            "no such intercept" /
            "no such node" /
            "no such request" /
            "no such script" /
            "no such storage partition" /
            "no such user context" /
            "session not created" /
            "unable to capture screen" /
            "unable to close browser" /
            "unable to set cookie" /
            "unable to set file input" /
            "underspecified storage partition" /
            "unknown command" /
            "unknown error" /
            "unsupported operation"

To obtain a list of event enabled navigables given session and event name:

1. Let navigables be an empty set.

2. For each navigable → events of session’s navigable event map:

   1. If events contains event name, append navigable to navigables

3. Return navigables.

The set of sessions for which an event is enabled given event name and navigables is:

1. Let sessions be a new set.

2. For each session in active BiDI sessions:

   1. If event is enabled with session, event name and navigables, append session to sessions.

3. Return sessions.

To determine if an event is enabled given session, event name and navigables:

Note: navigables is a set because a shared worker can be associated with multiple contexts.

1. Let top-level traversables be an empty set.

2. For each navigable of navigables, append navigable’s top-level traversable to top-level traversables.

3. Let event map be the navigable event map for session.

4. For each navigable of top-level traversables:

   1. If event map contains navigable, let navigable events be event map[navigable]. Otherwise let navigable events be null.

   2. If navigable events is not null, and navigable events contains event name, return true.

5. If the global event set for session contains event name return true.

6. Return false.

To obtain a set of event names given an name:

1. Let events be an empty set.

2. If name contains a U+002E (period):

   1. If name is the event name for an event, append name to events and return success with data events.

   2. Return an error with error code invalid argument

3. Otherwise name is interpreted as representing all the events in a module. If name is not a module name return an error with error code invalid argument.

4. Append the event name for each event in the module with name name to events.

5. Return success with data events.

To construct a WebSocket resource name given a session session:

1. If session is null, return "/session"

2. Return the result of concatenating the string "/session/" with session’s session ID.

To construct a WebSocket URL given a WebSocket listener listener and session session:

1. Let resource name be the result of construct a WebSocket resource name with session.

2. Return a WebSocket URI constructed with host set to listener’s host, port set to listener’s port, path set to resource name, following the wss-URI construct if listener’s secure flag is set and the ws-URL construct otherwise.

To get a session ID for a WebSocket resource given resource name:

1. If resource name doesn’t begin with the byte string "/session/", return null.

2. Let session id be the bytes in resource name following the "/session/" prefix.

3. If session id is not the string representation of a UUID, return null.

4. Return session id.

To start listening for a WebSocket connection given a session session:

1. If there is an existing WebSocket listener in active listeners which the remote end would like to reuse, let listener be that listener. Otherwise let listener be a new WebSocket listener with implementation-defined host, port, secure flag, and an empty list of WebSocket resources.

2. Let resource name be the result of construct a WebSocket resource name with session.

3. Append resource name to the list of WebSocket resources for listener.

4. Append listener to the remote end's active listeners.

5. Return listener.

To handle an incoming message given a WebSocket connection connection, type type and data data:

1. If type is not text, send an error response given connection, null, and invalid argument, and finally return.

2. Assert: data is a scalar value string, because the WebSocket handling errors in UTF-8-encoded data would already have failed the WebSocket connection otherwise.

   Nothing seems to define what status code is used for UTF-8 errors.

3. If there is a BiDi Session associated with connection connection, let session be that session. Otherwise if connection is in WebSocket connections not associated with a session, let session be null. Otherwise, return.

4. Let parsed be the result of parsing JSON into Infra values given data. If this throws an exception, then send an error response given connection, null, and invalid argument, and finally return.

5. If session is not null and not in active sessions then return.

6. Match parsed against the remote end definition. If this results in a match:

   1. Let matched be the map representing the matched data.

   2. Assert: matched contains "id", "method", and "params".

   3. Let command id be matched["id"].

   4. Let method be matched["method"]

   5. Let command be the command with command name method.

   6. If session is null and command is not a static command, then send an error response given connection, command id, and invalid session id, and return.

   7. Run the following steps in parallel:

      1. Let result be the result of running the remote end steps for command given session and command parameters matched["params"]

      2. If result is an error, then send an error response given connection, command id, and result’s error code, and finally return.

      3. Let value be result’s data.

      4. Assert: value matches the definition for the result type corresponding to the command with command name method.

      5. If method is "session.new", let session be the entry in the list of active sessions whose session ID is equal to the "sessionId" property of value, append connection to session’s session WebSocket connections, and remove connection from the WebSocket connections not associated with a session.

      6. Let response be a new map matching the CommandResponse production in the local end definition with the id field set to command id and the value field set to value.

      7. Let serialized be the result of serialize an infra value to JSON bytes given response.

      8. Send a WebSocket message comprised of serialized over connection.

7. Otherwise:

   1. Let command id be null.

   2. If parsed is a map and parsed["id"] exists and is an integer greater than or equal to zero, set command id to that integer.

   3. Let error code be invalid argument.

   4. If parsed is a map and parsed["method"] exists and is a string, but parsed["method"] is not in the set of all command names, set error code to unknown command.

   5. Send an error response given connection, command id, and error code.

To get related navigables given an settings object settings:

1. Let related navigables be an empty set.

2. Let navigable be null.

3. If settings’ relevant global object is a Window, set navigable to relevant global object's associated Document’s node navigable.

   Otherwise if the global object specified by settings is a WorkerGlobalScope, for each owner in the global object's owner set, if owner is a Document, set navigable to owner’s node navigable.

4. If navigable is not null, append navigable to related navigables.

5. Return related navigables.

To emit an event given session, and body:

1. Assert: body has size 2 and contains "method" and "params".

2. Let serialized be the result of serialize an infra value to JSON bytes given body.

3. For each connection in session’s session WebSocket connections:

   1. Send a WebSocket message comprised of serialized over connection.

To send an error response given a WebSocket connection connection, command id, and error code:

1. Let error data be a new map matching the ErrorResponse production in the local end definition, with the id field set to command id, the error field set to error code, the message field set to an implementation-defined string containing a human-readable definition of the error that occurred and the stacktrace field optionally set to an implementation-defined string containing a stack trace report of the active stack frames at the time when the error occurred.

2. Let response be the result of serialize an infra value to JSON bytes given error data.

   Note: command id can be null, in which case the id field will also be set to null, not omitted from response.

3. Send a WebSocket message comprised of response over connection.

To handle a connection closing given a WebSocket connection connection:

1. If there is a BiDi session associated with connection connection:

   1. Let session be the BiDi session associated with connection connection.

   2. Remove connection from session’s session WebSocket connections.

2. Otherwise, if WebSocket connections not associated with a session contains connection, remove connection from that set.

To close the WebSocket connections given session:

1. For each connection in session’s session WebSocket connections:

   1. Start the WebSocket closing handshake with connection.

      Note: this will result in the steps in handle a connection closing being run for connection, which will clean up resources associated with connection.

The WebDriver new session algorithm defined by this specification, with parameters session, capabilities, and flags is:

1. If flags contains "bidi", return.

2. Let webSocketUrl be the result of getting a property named "webSocketUrl" from capabilities.

3. If webSocketUrl is undefined, return.

4. Assert: webSocketUrl is true.

5. Let listener be the result of start listening for a WebSocket connection given session.

6. Set webSocketUrl to the result of construct a WebSocket URL with listener and session.

7. Set a property on capabilities named "webSocketUrl" to webSocketUrl.

8. Set session’s BiDi flag to true.

9. Append "bidi" to flags.

Implementations should also allow clients to establish a BiDi Session which is not a HTTP Session. In this case the URL to the WebSocket server is communicated out-of-band. An implementation that allows this supports BiDi-only sessions. At the time such an implementation is ready to accept requests to start a WebDriver session, it must:

1. Start listening for a WebSocket connection given null.

To get or create a sandbox realm given name and navigable:

1. If name is an empty string, then return error with error code invalid argument.

2. Let window be navigable’s active window.

3. If sandbox map does not contain window, set sandbox map[window] to a new map.

4. Let sandboxes be sandbox map[window].

5. If sandboxes does not contain name, set sandboxes[name] to create a sandbox realm with navigable.

6. Return success with data sandboxes[name].

To create a sandbox realm with window:

Define creation of sandbox realm. This is going to return a SandboxWindowProxy wrapping window.

To get a sandbox name given target realm:

1. Let realms maps be get the values of sandbox map.

2. For each realms map in realms maps:

   1. For each name → realm in realms map:

      1. If realm is target realm, return name.

3. Return null.

To get unwrapped object:

1. While object is SandboxProxy or SandboxWindowProxy, set object to it’s wrapped object.

2. Return object.

To get user context given user context id:

1. For each user context in the set of user contexts:

2. If user context’s user context id equals user context id:

   1. Return user context.

3. Return null.

SessionCommand = (
  session.End //
  session.New //
  session.Status //
  session.Subscribe //
  session.Unsubscribe
)

SessionResult = (
   session.NewResult /
   session.StatusResult
)

To end the session given session:

1. Remove session from active sessions.

2. If active sessions is empty, set the webdriver-active flag to false.

To cleanup the session given session:

1. Close the WebSocket connections with session.

2. If active sessions is empty, cleanup remote end state.

3. Perform any implementation-specific cleanup steps.

To cleanup remote end state.

1. Clear the before request sent map.

2. Set the default cache behavior to "default".

3. Clear the navigable cache behavior map.

4. Perform implementation-defined steps to enable any implementation-specific resource caches that are usually enabled in the current remote end configuration.

To update the event map, given session, requested event names, navigables, and enabled:

Note: The return value of this algorithm is a map between event names and navigables. When the events are being enabled, the navigables in the return value are those for which the event are now enabled but were not previously. When events are disabled, the return value is always empty.

1. Let global event set be a clone of the global event set for session.

2. Let event map be a new map.

3. For each key → value of the navigable event map for session:

   1. Set event map[key] to a clone of value.

4. Let event names be an empty set.

5. For each entry name in requested event names, let event names be the union of event names and the result of trying to obtain a set of event names with name.

6. Let enabled events be a new map.

7. If navigables is null:

   1. If enabled is true:

      1. For each event name of event names:

         1. If global event set doesn’t contain event name:

            1. Let already enabled navigables be the event enabled navigables given session and event name.

            2. Add event name to global event set.

            3. For each navigable of already enabled navigables, remove event name from event map[navigable].

            4. Let newly enabled contexts be a list of all top-level traversable that are not contained in already enabled navigables,

            5. Set enabled events[event name] to newly enabled contexts.

   2. If enabled is false:

      1. For each event name in event names:

         1. If global event set contains event name, remove event name from global event set. Otherwise return error with error code invalid argument.

8. Otherwise, if navigables is not null:

   1. Let targets be an empty map.

   2. For each navigable id in navigables:

      1. Let navigable be the result of trying to get a navigable with navigable id.

      2. Let top-level traversable be the top-level traversable for navigable.

      3. If event map does not contain top-level traversable, set event map[top-level traversable] to a new set.

      4. Set targets[top-level traversable] to event map[top-level traversable].

   3. For each event name in event names:

      1. If enabled is true and global event set contains event name, continue.

      2. For each navigable → target in targets:

         1. If enabled is true and target does not contain event name:

            1. Add event name to target.

            2. If enabled events does not contain event name, set enabled events[event name] to a new set.

            3. Append navigable to enabled events[event name].

         2. If enabled is false:

            1. If target contains event name, remove event name from target. Otherwise return error with error code invalid argument.

9. Set the global event set for session to global event set.

10. Set the navigable event map for session to event map.

11. Return success with data enabled events.

Note: Implementations that do additional work when an event is enabled, e.g. subscribing to the relevant engine-internal events, will likely perform those additional steps when updating the event map. This specification uses a model where hooks are always called and then the event map is used to filter only those that ought to be returned to the local end.

session.CapabilitiesRequest = {
  ? alwaysMatch: session.CapabilityRequest,
  ? firstMatch: [*session.CapabilityRequest]
}

session.CapabilityRequest = {
  ? acceptInsecureCerts: bool,
  ? browserName: text,
  ? browserVersion: text,
  ? platformName: text,
  ? proxy: session.ProxyConfiguration,
  ? unhandledPromptBehavior: session.UserPromptHandler,
  Extensible
};

The additional capability deserialization algorithm for the "webSocketUrl" capability, with parameter value is:

1. If value is not a boolean, return error with code invalid argument.

2. Return success with data value.

The matched capability serialization algorithm for the "webSocketUrl" capability, with parameter value is:

1. If value is false, return success with data null.

2. Return success with data true.

session.ProxyConfiguration = {
   session.AutodetectProxyConfiguration //
   session.DirectProxyConfiguration //
   session.ManualProxyConfiguration //
   session.PacProxyConfiguration //
   session.SystemProxyConfiguration //
}

session.AutodetectProxyConfiguration = (
   proxyType: "autodetect",
   Extensible
)

session.DirectProxyConfiguration = (
   proxyType: "direct",
   Extensible
)

session.ManualProxyConfiguration = (
   proxyType: "manual",
   ? ftpProxy: text,
   ? httpProxy: text,
   ? sslProxy: text,
   ? session.SocksProxyConfiguration,
   ? noProxy: [*text],
   Extensible
)

session.SocksProxyConfiguration = (
   socksProxy: text,
   socksVersion: 0..255,
)

session.PacProxyConfiguration = (
   proxyType: "pac",
   proxyAutoconfigUrl: text,
   Extensible
)

session.SystemProxyConfiguration = (
   proxyType: "system"
   Extensible
)

session.UserPromptHandler = {
  ? alert: session.UserPromptHandlerType,
  ? beforeUnload: session.UserPromptHandlerType,
  ? confirm: session.UserPromptHandlerType,
  ? default: session.UserPromptHandlerType,
  ? prompt: session.UserPromptHandlerType,
};

session.UserPromptHandlerType = "accept" / "dismiss" / "ignore";

session.SubscriptionRequest = {
  events: [+text],
  ? contexts: [+browsingContext.BrowsingContext],
}

The remote end steps given session, and command parameters are:

1. Let body be a new map 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

The remote end steps given session and command parameters are:

1. If session is not null, return an error with error code session not created.

2. If the implementation is unable to start a new session for any reason, return an error with error code session not created.

3. Let flags be a set containing "bidi".

4. Let capabilities json be the result of trying to process capabilities with command parameters and flags.

5. Let capabilities be convert a JSON-derived JavaScript value to an Infra value with capabilities json.

6. Let session be the result of trying to create a session with capabilities and flags.

7. Set session’s BiDi flag to true.

   Note: the connection for this session will be set to the current connection by the caller.

8. Let body be a new map matching the session.NewResult production, with the sessionId field set to session’s session ID, and the capabilities field set to capabilities.

9. Return success with data body.

The remote end steps given session and command parameters are:

1. End the session with session.

2. Return success with data null, and in parallel run the following steps:

   1. Wait until the Send a WebSocket message steps have been called with the response to this command.

      this is rather imprecise language, but hopefully it’s clear that the intent is that we send the response to the command before starting shutdown of the connections.

   2. Cleanup the session with session.

The remote end steps with session and command parameters are:

1. Let the list of event names be the value of the events field of command parameters

2. Let the list of navigables be the value of the contexts field of command parameters if it is present or null if it isn’t.

3. Let enabled events be the result of trying to update the event map with session, list of event names , list of navigables and enabled true.

4. Let subscribe step events be a new map.

5. For each event name → navigables in enabled events:

   1. If the event with event name event name defines remote end subscribe steps, set subscribe step events[event name] to navigables.

6. Sort in ascending order subscribe step events using the following less than algorithm given two entries with keys event name one and event name two:

   1. Let event one be the event with name event name one

   2. Let event two be the event with name event name two

   3. Return true if event one’s subscribe priority is less than event two’s subscribe priority, or false otherwise.

7. If list of navigables is null, let include global be true, otherwise let include global be false.

8. For each event name → navigables in subscribe step events:

   1. Run the remote end subscribe steps for the event with event name event name given session, navigables and include global.

9. Return success with data null.

The remote end steps with session and command parameters are:

1. Let the list of event names be the value of the events field of command parameters.

2. Let the list of contexts be the value of the contexts field of command parameters if it is present or null if it isn’t.

3. Try to update the event map with session, list of event names, list of contexts and enabled false.

4. Return success with data null.

BrowserCommand = (
  browser.Close //
  browser.CreateUserContext //
  browser.GetClientWindows //
  browser.GetUserContexts //
  browser.RemoveUserContext //
  browser.SetClientWindowState //
)

BrowserResult = (
   browser.CreateUserContextResult /
   browser.GetUserContextsResult
)

To get the client window state given window:

1. Let documents be an empty list.

2. Let visible documents be an empty list.

3. For each top-level traversable traversable:

   1. If traversable’s client window is not window then continue.

   2. Let document be traversable’s active document.

   3. Append document to documents.

   4. If document’s visibility state is "visible", Append document to visible documents.

4. For each document in visible documents:

   1. If document’s fullscreen element is not null, return "fullscreen".

5. If visible documents is empty but documents is not empty, or if window is otherwise in an OS-specific minimized state, return "minimized".

   Note: This will usually, but not necessarily, mean that window’s width and height are equal to 0.

6. If window is in an OS-specific maximized state return "maximized".

   Note: This will usually, but not necessarily, mean that window’s width is equal to the width of the web-exposed screen area and window’s height is equal to the height of the web-exposed screen area.

7. Return "normal".

To set the client window state given window and state:

1. Let current state be get the client window state with window.

2. If current state is equal to state, return success with data null.

3. Switch on the value of state:

   "fullscreen"

   If not fullscreen is supported return error with error code unsupported operation.

   "normal"

   If not restore client window is supported for window return error with error code unsupported operation.

   "maximize"

   If not maximize client window is supported for window return error with error code unsupported operation.

   "minimize"

   If not minimize client window is supported for window return error with error code unsupported operation.

4. Let documents be an empty list.

5. For each top-level traversable traversable:

   1. If traversable’s associated client window is not window then continue.

   2. Let document be traversable’s active document.

   3. Append document to documents.

6. If documents is empty return error with error code no such client window.

7. If current state is "fullscreen":

   1. For each document in documents:

      1. Fully exit fullscreen with document.

         Note: This is a no-op for documents in window that are not fullscreen.

8. Switch on the value of state:

   "fullscreen"

   1. For each document in documents:

      1. If document’s visibility state is "visible", fullscreen an element with document’s document element.

      2. Break.

   "normal"

   1. Restore the client window window.

   "maximize

   1. Maximize the client window window.

   "minimize

   1. Minimize the client window window.

9. Return success with data null.

browser.ClientWindow = text;

browser.ClientWindowInfo = {
  active: bool,
  clientWindow: browser.ClientWindow,
  height: js-uint,
  state: "fullscreen" / "maximized" / "minimized" / "normal",
  width: js-uint,
  x: js-int,
  y: js-int,
}

To get the client window info given client window:

1. Let client window id be the client window id for client window.

2. Let state be get the client window state with client window.

3. If client window can receive keyboard input channeled from the operating system, let active be true, otherwise let active be false.

   Note: This could mean that a top-level traversable whose client window is client window has system focus, or it could mean that the user interface of the browser itself currently has focus.

4. Let client window info be a map matching the browser.ClientWindowsInfo production with the clientWindow field set to client window id, state field set to state, the x field set to client window’s x-coordinate, the y field set to client window’s y-coordinate, the width field set to client window’s width, the height field set to client window’s height, and the active field set to active.

5. Return client window info

browser.UserContext = text;

browser.UserContextInfo = {
  userContext: browser.UserContext
}

The remote end steps with session and command parameters are:

1. End the session with session.

2. If active sessions is not empty an implementation may return error with error code unable to close browser, and then run the following steps in parallel:

   1. Wait until the Send a WebSocket message steps have been called with the response to this command.

   2. Cleanup the session with session.

   Note: The behaviour in cases where the browser has multiple automation sessions is currently unspecified. It might be that any session can close the browser, or that only the final open session can actually close the browser, or only the first session started can. This behaviour might be fully specified in a future version of this specification.

3. For each active session in active sessions:

   1. End the session active session.

   2. Cleanup the session with active session

4. Return success with data null, and run the following steps in parallel.

   1. Wait until the Send a WebSocket message steps have been called with the response to this command.

   2. Cleanup the session with session.

   3. Close any top-level traversables without prompting to unload.

   4. Perform implementation defined steps to clean up resources associated with the remote end under automation.

      Note: For example this might include cleanly shutting down any OS-level processes associated with the browser under automation, removing temporary state, such as user profile data, created by the remote end while under automation, or shutting down the WebSocket Listener. Because of differences between browsers and operating systems it is not possible to specify in detail precise invariants local ends can depend on here.

The remote end steps are:

1. Let user context be a new user context.

2. Append user context to the set of user contexts.

3. Let user context info be a map matching the browser.UserContextInfo production with the userContext field set to user context’s user context id.

4. Return success with data user context info.

The remote end steps are:

1. Let client window ids be an empty set.

2. Let client windows be an empty list.

3. For each top-level traversable traversable:

   1. Let client window be traversable’s associated client window

   2. Let client window id be the client window id for client window.

   3. If client window ids contains client window id, continue.

   4. Append client window id to client window ids.

   5. Let client window info be get the client window info with client window.

   6. Append client window info to client windows.

4. Let result be a map matching the browser.GetClientWindowsResult production with the clientWindows field set to client windows.

5. Return success with data result.

The remote end steps are:

1. Let user contexts be an empty list.

2. For each user context in the set of user contexts:

   1. Let user context info be a map matching the browser.UserContextInfo production with the userContext field set to user context’s user context id.

   2. Append user context info to user contexts.

3. Let result be a map matching the browser.GetUserContextsResult production with the userContexts field set to user contexts.

4. Return success with data result.

The remote end steps with command parameters are:

1. Let user context id be command parameters["userContext"].

2. If user context id is "default", return error with error code invalid argument.

3. Set user context to get user context with user context id.

4. If user context is null, return error with error code no such user context.

5. For each top-level traversable navigable:

   1. If navigable’s associated user context is user context:

      1. Close navigable without prompting to unload.

6. Remove user context for the set of user contexts.

7. Return success with data null.

The remote end steps with session and command parameters are:

1. If the implementation does not support setting the client window state at all, then return error with error code unsupported operation.

2. If there is a client window with client window id command parameters["clientWindow"], let client window be that client window. Otherwise return error with error code no such client window.

3. Try to set the client window state with client window and command parameters["state"].

4. If command parameters["state"] is "normal":

   1. If command parameters contains "x" and the implementation supports positioning client windows, set the x-coordinate of client window to a value that is as close as possible command parameters["x"].

   2. If command parameters contains "y" and the implementation supports positioning client windows, set the y-coordinate of client window to a value that is as close as possible command parameters["y"].

   3. If command parameters contains "width" and the implementation supports resizing client windows, set the width of client window to a value that is as close as possible command parameters["width"].

   4. If command parameters contains "width" and the implementation supports resizing client windows, set the width of client window to a value that is as close as possible command parameters["width"].

5. Let client window info be get the client window info with client window.

6. Return success with data client window info.

Note: For simplicity this models all client window operations as synchronous. Therefore the returned client window dimensions are expected to be those after the window has reached its new state.

BrowsingContextCommand = (
  browsingContext.Activate //
  browsingContext.CaptureScreenshot //
  browsingContext.Close //
  browsingContext.Create //
  browsingContext.GetTree //
  browsingContext.HandleUserPrompt //
  browsingContext.LocateNodes //
  browsingContext.Navigate //
  browsingContext.Print //
  browsingContext.Reload //
  browsingContext.SetViewport //
  browsingContext.TraverseHistory
)

BrowsingContextResult = (
  browsingContext.CaptureScreenshotResult /
  browsingContext.CreateResult /
  browsingContext.GetTreeResult /
  browsingContext.LocateNodesResult /
  browsingContext.NavigateResult /
  browsingContext.PrintResult /
  browsingContext.TraverseHistoryResult
)

BrowsingContextEvent = (
  browsingContext.ContextCreated //
  browsingContext.ContextDestroyed //
  browsingContext.DomContentLoaded //
  browsingContext.DownloadWillBegin //
  browsingContext.FragmentNavigated //
  browsingContext.HistoryUpdated //
  browsingContext.Load //
  browsingContext.NavigationAborted //
  browsingContext.NavigationFailed //
  browsingContext.NavigationStarted //
  browsingContext.UserPromptClosed //
  browsingContext.UserPromptOpened
)

browsingContext.BrowsingContext = text;

To get a navigable given navigable id:

1. If navigable id is null, return success with data null.

2. If there is no navigable with navigable id navigable id return error with error code no such frame

3. Let navigable be the navigable with id navigable id.

4. Return success with data navigable.

browsingContext.InfoList = [*browsingContext.Info]

browsingContext.Info = {
  children: browsingContext.InfoList / null,
  clientWindow: browser.ClientWindow,
  context: browsingContext.BrowsingContext,
  originalOpener: browsingContext.BrowsingContext / null,
  url: text,
  userContext: browser.UserContext,
  ? parent: browsingContext.BrowsingContext / null,
}

To get the parent navigable given navigable:

1. Let parent navigable be navigable’s parent.

2. If parent navigable is null, then return null.

3. Return parent navigable.

To get the child navigables given navigable:

TODO: make this return a list in document order

1. Let child navigables be a set containing all navigables that are a child navigable of navigable.

2. Return child navigables.

To get the navigable info given navigable, max depth and include parent id:

1. Let navigable id be the navigable id for navigable.

2. Let navigable be get the parent navigable given navigable.

3. If navigable is not null let parent id be the navigable id of navigable. Otherwise let parent id be null.

4. Let document be navigable’s active document.

5. Let url be the result of running the URL serializer, given document’s URL.

   Note: This includes the fragment component of the URL.

6. Let child infos be null.

7. If max depth is null, or max depth is greater than 0:

   1. Let child navigables be get the child navigables given navigable.

   2. Let child depth be max depth - 1 if max depth is not null, or null otherwise.

   3. Set child infos to an empty list.

   4. For each child navigable of child navigables:

      1. Let info be the result of get the navigable info given child navigable, child depth, and false.

      2. Append info to child infos

8. Let user context be navigable’s associated user context.

9. Let opener id be the navigable id for navigable’s original opener, if navigable’s original opener is not null, and null otherwise.

10. Let top-level traversable be navigable’s top-level traversable.

11. Let client window id be the client window id for top-level traversable’s associated client window.

12. Let navigable info be a map matching the browsingContext.Info production with the context field set to navigable id, the parent field set to parent id if include parent id is true, or unset otherwise, the url field set to url, the userContext field set to user context’s user context id, originalOpener field set to opener id, the children field set to child infos, and the clientWindow field set to client window id.

13. Return navigable info.

To await a navigation given navigable, request, wait condition, and optionally history handling (default: "default") and ignore cache (default: false):

1. Let navigation id be the string representation of a UUID based on truly random, or pseudo-random numbers.

2. Navigate navigable with resource request, and using navigable’s active document as the source Document, with navigation id navigation id, and history handling behavior history handling. If ignore cache is true, the navigation must not load resources from the HTTP cache.

   property specify how the ignore cache flag works. This needs to consider whether only the first load of a resource bypasses the cache (i.e. whether this is like initially clearing the cache and proceeding like normal), or whether resources not directly loaded by the HTML parser (e.g. loads initiated by scripts or stylesheets) also bypass the cache.

3. Let (event received, navigate status) be await given «"navigation started", "navigation failed", "fragment navigated"», and navigation id.

4. Assert: navigate status’s id is navigation id.

5. If navigate status’s status is "complete":

   1. Let body be a map matching the browsingContext.NavigateResult production, with the navigation field set to navigation id, and the url field set to the result of the URL serializer given navigate status’s url.

   2. Return success with data body.

   Note: this is the case if the navigation only caused the fragment to change.

6. If navigate status’s status is "canceled" return error with error code unknown error.

   TODO: is this the right way to handle errors here?

7. Assert: navigate status’s status is "pending" and navigation id is not null.

8. If wait condition is "none":

   1. Let body be a map matching the browsingContext.NavigateResult production, with the navigation field set to navigation id, and the url field set to the result of the URL serializer given navigate status’s url.

   2. Return success with data body.

9. If wait condition is "interactive", let event name be "domContentLoaded", otherwise let event name be "load".

10. Let (event received, status) be await given «event name, "download started", "navigation aborted", "navigation failed"» and navigation id.

11. If event received is "navigation failed" return error with error code unknown error.

    Are we surfacing enough information about what failed and why with an error here? What error code do we want? Is there going to be a problem where local ends parse the implementation-defined strings to figure out what actually went wrong?

12. Let body be a map matching the browsingContext.NavigateResult production, with the navigation field set to status’s id, and the url field set to the result of the URL serializer given status’s url.

13. Return success with data body.

browsingContext.Locator = (
   browsingContext.AccessibilityLocator /
   browsingContext.CssLocator /
   browsingContext.InnerTextLocator /
   browsingContext.XPathLocator
)

browsingContext.AccessibilityLocator = {
   type: "accessibility",
   value: {
    ? name: text,
    ? role: text,
   }
}

browsingContext.CssLocator = {
   type: "css",
   value: text
}

browsingContext.InnerTextLocator = {
   type: "innerText",
   value: text,
   ? ignoreCase: bool
   ? matchType: "full" / "partial",
   ? maxDepth: js-uint,
}

browsingContext.XPathLocator = {
   type: "xpath",
   value: text
}

browsingContext.Navigation = text;

browsingContext.NavigationInfo = {
  context: browsingContext.BrowsingContext,
  navigation: browsingContext.Navigation / null,
  timestamp: js-uint,
  url: text,
}

To get the navigation info, given navigable and navigation status:

1. Let navigable id be the navigable id for navigable.

2. Let navigation id be navigation status’s id.

3. Let timestamp be a time value representing the current date and time in UTC.

4. Let url be navigation status’s url.

5. Return a map matching the browsingContext.NavigationInfo production, with the context field set to navigable id, the navigation field set to navigation id, the timestamp field set to timestamp, and the url field set to the result of the URL serializer given url.

browsingContext.ReadinessState = "none" / "interactive" / "complete"

browsingContext.UserPromptType = "alert" / "beforeunload" / "confirm" / "prompt";

The remote end steps with command parameters are:

1. Let navigable id be the value of the command parameters["context"] field.

2. Let navigable be the result of trying to get a navigable with navigable id.

3. If navigable is not a top-level traversable, return error with error code invalid argument.

4. Return activate a navigable with navigable.

To activate a navigable given navigable:

1. Run implementation-specific steps so that navigable’s system visibility state becomes visible. If this is not possible return error with error code unsupported operation.

   Note: This can have the side effect of making currently visible navigables hidden.

   Note: This can change the underlying OS state by causing the window to become unminimized or by other side effects related to changing the system visibility state.

2. Run implementation-specific steps to set the system focus on the navigable if it is not focused.

   Note: This does not change the focused area of the document except as mandated by other specifications.

3. Return success with data null.

To normalize rect given rect:

Note: This ensures that the resulting rect has positive width dimension and height dimension.

1. Let x be rect’s x coordinate.

2. Let y be rect’s y coordinate.

3. Let width be rect’s width dimension.

4. Let height be rect’s height dimension.

5. If width is less than 0, set x to x + width and then set width to -width.

6. If height is less than 0, set y to y + height and then set height to -height.

7. Return a new DOMRectReadOnly with x coordinate x, y coordinate y, width dimension width and height dimension height.

To rectangle intersection given rect1 and rect2

1. Let rect1 be normalize rect with rect1.

2. Let rect2 be normalize rect with rect2.

3. Let x1_0 be rect1’s x coordinate.

4. Let x2_0 be rect2’s x coordinate.

5. Let x1_1 be rect1’s x coordinate plus rect1’s width dimension.

6. Let x2_1 be rect2’s x coordinate plus rect2’s width dimension.

7. Let x_0 be the maximum element of «x1_0, x2_0».

8. Let x_1 be the minimum element of «x1_1, x2_1».

9. Let y1_0 be rect1’s y coordinate.

10. Let y2_0 be rect2’s y coordinate.

11. Let y1_1 be rect1’s y coordinate plus rect1’s height dimension.

12. Let y2_1 be rect2’s y coordinate plus rect2’s height dimension.

13. Let y_0 be the maximum element of «y1_0, y2_0».

14. Let y_1 be the minimum element of «y1_1, y2_1».

15. If x_1 is less than x_0, let width be 0. Otherwise let width be x_1 - x_0.

16. If y_1 is less than y_0, let height be 0. Otherwise let height be y_1 - y_0.

17. Return a new DOMRectReadOnly with x coordinate x_0, y coordinate y_0, width dimension width and height dimension height.

To render document to a canvas given document and rect:

1. Let ratio be determine the device pixel ratio given document’s default view.

2. Let paint width be rect’s width dimension multiplied by ratio, rounded to the nearest integer, so it matches the width of rect in device pixels.

3. Let paint height be rect’s height dimension multiplied by ratio, rounded to the nearest integer, so it matches the height of rect in device pixels.

4. Let canvas be a new HTMLCanvasElement with width paint width and height paint height.

5. Let canvas context be the result of running the 2D context creation algorithm with canvas and null.

6. Set canvas’s context mode to 2D.

7. Complete implementation specific steps equivalent to drawing the region of the framebuffer representing the region of document covered by rect to canvas context, such that each pixel in the framebuffer corresponds to a pixel in canvas context with (rect’s x coordinate, rect’s y coordinate) in viewport coordinates corresponding to (0,0) in canvas context and (rect’s x coordinate + rect’s width dimension, rect’s y coordinate + rect’s height dimension) corresponding to (paint width, paint height).

8. Return canvas.

To encode a canvas as Base64 given canvas and format:

1. If format is not null, let type be the type field of format, and let quality be the quality field of format.

2. Otherwise, let type be "image/png" and let quality be undefined.

3. Let file be a serialization of the bitmap as a file for canvas with type and quality.

4. Let encoded string be the forgiving-base64 encode of file.

5. Return success with data encoded string.

To get the origin rectangle given document and origin:

1. If origin is "viewport":

   1. Let viewport be document’s visual viewport.

   2. Let viewport rect be a DOMRectReadOnly with x coordinate viewport page left, y coordinate viewport page top, width dimension viewport width, and height dimension viewport height.

   3. Return success with data viewport rect.

2. Assert: origin is "document".

3. Let document element be the document element for document.

4. Let document rect be a DOMRectReadOnly with x coordinate 0, y coordinate 0, width dimension document element scroll height, and height dimension document element scroll width.

5. Return success with data document rect.

The remote end steps with command parameters are:

1. Let navigable id be the value of the context field of command parameters.

2. Let prompt unload be the value of the promptUnload field of command parameters.

3. Let navigable be the result of trying to get a navigable with navigable id.

4. Assert: navigable is not null.

5. If navigable is not a top-level traversable, return error with error code invalid argument.

6. If prompt unload is true:

   1. Close navigable.

7. Otherwise:

   1. Close navigable without prompting to unload.

8. Return success with data null.

There is an open discussion about the behavior when closing the last top-level traversable. We could expect to close the browser, close the session or leave this up to the implementation. [Issue #w3c/webdriver-bidi#170]

The remote end steps with command parameters are:

1. Let type be the value of the type field of command parameters.

2. Let reference navigable id be the value of the referenceContext field of command parameters, if present, or null otherwise.

3. If reference navigable id is not null, let reference navigable be the result of trying to get a navigable with reference navigable id. Otherwise let reference navigable be null.

4. If reference navigable is not null and is not a top-level traversable, return error with error code invalid argument.

5. If the implementation is unable to create a new top-level traversable for any reason then return error with error code unsupported operation.

6. Let user context be the default user context if reference navigable is null, and reference navigable’ associated user context otherwise.

7. Let user context id be the value of the userContext field of command parameters if present, or null otherwise.

8. If user context id is not null, set user context to the result of trying to get user context with user context id.

9. If user context is null, return error with error code no such user context.

10. If the implementation is unable to create a new top-level traversable with associated user context user context for any reason, return error with error code unsupported operation.

11. Let traversable be the result of trying to create a new top-level traversable steps with null and empty string, and setting the associated user context for the newly created top-level traversable to user context. Which OS window the new top-level traversable is created in depends on type and reference navigable:

    • If type is "tab" and the implementation supports multiple top-level traversables in the same OS window:

      • The new top-level traversable should reuse an existing OS window, if any.

      • If reference navigable is not null, the new top-level traversable should reuse the window containing reference navigable, if any. If the top-level traversables inside an OS window have a definite ordering, the new top-level traversable should be immediately after reference navigable’s top-level traversable in that ordering.

    • If type is "window", and the implementation supports multiple top-level traversable in separate OS windows, the created top-level traversable should be in a new OS window.

    • Otherwise, the details of how the top-level traversable is presented to the user are implementation defined.

12. If the value of the command parameters’ background field is false:

    1. Let activate result be the result of activate a navigable with the newly created navigable.

    2. If activate result is an error, return activate result.

    Note: Do not invoke the focusing steps for the created navigable if background is true.

13. Let body be a map matching the browsingContext.CreateResult production, with the context field set to traversable’s navigable id.

14. Return success with data body.

The remote end steps with session and command parameters are:

1. Let root id be the value of the root field of command parameters if present, or null otherwise.

2. Let max depth be the value of the maxDepth field of command parameters if present, or null otherwise.

3. Let navigables be an empty list.

4. If root id is not null, append the result of trying to get a navigable given root id to navigables. Otherwise append all top-level traversables to navigables.

5. Let navigables infos be an empty list.

6. For each navigable of navigables:

   1. Let info be the result of get the navigable info given navigable, max depth, and true.

   2. Append info to navigables infos

7. Let body be a map matching the browsingContext.GetTreeResult production, with the contexts field set to navigables infos.

8. Return success with data body.

The remote end steps with session and command parameters are:

1. Let navigable id be the value of the context field of command parameters.

2. Let navigable be the result of trying to get a navigable with navigable id.

3. Let accept be the value of the accept field of command parameters if present, or true otherwise.

4. Let userText be the value of the userText field of command parameters if present, or the empty string otherwise.

5. If navigable is currently showing a simple dialog from a call to alert then acknowledge the prompt.

   Otherwise if navigable is currently showing a simple dialog from a call to confirm, then respond positively if accept is true, or respond negatively if accept is false.

   Otherwise if navigable is currently showing a simple dialog from a call to prompt, then respond with the string value userText if accept is true, or abort if accept is false.

   Otherwise, if navigable is currently showing a prompt as part of the prompt to unload steps, then confirm the navigation if accept is true, otherwise refuse the navigation.

   Otherwise return error with error code no such alert.

6. Return success with data null.

To locate nodes using CSS with given navigable, context nodes, selector, maximum returned node count, and session:

1. Let returned nodes be an empty list.

2. Let parse result be the result of parse a selector given selector.

3. If parse result is failure, return error with error code invalid selector.

4. For each context node of context nodes:

   1. Let elements be the result of match a selector against a tree with parse result and navigable’s active document root using scoping root context node.

   2. For each element in elements:

      1. Append element to returned nodes.

      2. If maximum returned node count is not null and size of returned nodes is equal to maximum returned node count, return success with data returned nodes.

5. Return success with data returned nodes.

To locate nodes using XPath with given navigable, context nodes, selector, and maximum returned node count:

Note: Owing to the unmaintained state of the XPath specification, this algorithm is phrased as if making calls to the XPath DOM APIs. However this is to be understood as equivalent to spec-internal calls directly accessing the underlying algorithms, without going via the ECMAScript runtime.

1. Let returned nodes be an empty list.

2. For each context node of context nodes:

   1. Let evaluate result be the result of calling evaluate on navigable’s active document, with arguments selector, context node, null, ORDERED_NODE_SNAPSHOT_TYPE, and null. If this throws a "SyntaxError" DOMException, return error with error code invalid selector; otherwise, if this throws any other exception return error with error code unknown error.

   2. Let index be 0.

   3. Let length be the result of getting the snapshotLength property from evaluate result.

   4. Repeat, while index is less than length:

      1. Let node be the result of calling snapshotItem with evaluate result as this and index as the argument.

      2. Append node to returned nodes.

      3. If maximum returned node count not null and size of returned nodes is equal to maximum returned node count, return success with data returned nodes.

      4. Set index to index + 1.

3. Return success with data returned nodes.

To locate nodes using inner text with given context nodes, selector, max depth, match type, ignore case, and maximum returned node count:

1. If selector is the empty string, return error with error code invalid selector.

2. Let returned nodes be an empty list.

3. If ignore case is false, let search text be selector. Otherwise, let search text be the result of toUppercase with selector according to the Unicode Default Case Conversion algorithm.

4. For each context node in context nodes:

   1. If context node implements Document or DocumentFragment:

      Note: when traversing the document or document fragment, max depth is not decreased intentionally to make the search result with document and document.documentElement equivalent.

      1. Let child nodes be an empty list.

      2. For each node child in the children of context node.

         1. Append child to child nodes.

      3. Extend returned nodes with the result of trying to locate nodes using inner text with child nodes, selector, max depth, match type, ignore case, and maximum returned node count.

   2. If context node does not implement HTMLElement then continue.

   3. Let node inner text be the result of calling the innerText getter steps with context node as the this value.

   4. If ignore case is false, let node text be node inner text. Otherwise, let node text be the result of toUppercase with node inner text according to the Unicode Default Case Conversion algorithm.

   5. If search text is a code point substring of node text, perform the following steps:

      1. Let child nodes be an empty list and, for each node child in the children of context node:

         1. Append child to child nodes.

      2. If size of child nodes is equal to 0 or max depth is equal to 0, perform the following steps:

         1. If match type is "full" and node text is search text, append context node to returned nodes.

         2. Otherwise, if match type is "partial", append context node to returned nodes.

      3. Otherwise, perform the following steps:

         1. Let child max depth be null if max depth is null, or max depth - 1 otherwise.

         2. Let child node matches be the result of locate nodes using inner text with child nodes, selector, child max depth , match type, ignore case, and maximum returned node count.

         3. If size of child node matches is equal to 0 and match type is "partial", append context node to returned nodes. Otherwise, extend returned nodes with child node matches.

5. If maximum returned node count is not null, remove all entries in returned nodes with an index greater than or equal to maximum returned node count.

6. Return success with data returned nodes.

To collect nodes using accessibility attributes with given context nodes, selector, maximum returned node count, and returned nodes:

1. If returned nodes is null:

   1. Set returned nodes to an empty list.

2. For each context node in context nodes:

   1. Let match be true.

   2. If context node implements Element:

      1. If selector contains "role":

         1. Let role be the computed role of context node.

         2. If selector["role"] is not role:

            1. Set match to false.

      2. If selector contains "name":

         1. Let name be the accessible name of context node.

         2. If selector["name"] is not name:

            1. Set match to false.

   3. Otherwise, set match to false.

   4. If match is true:

      1. If maximum returned node count is not null and size of returned nodes is equal to maximum returned node count, break.

      2. Append context node to returned nodes.

   5. Let child nodes be an empty list and, for each node child in the children of context node:

      1. If child implements Element, append child to child nodes.

   6. Try to collect nodes using accessibility attributes with child nodes, selector, maximum returned node count, and returned nodes.

3. Return returned nodes.

To locate nodes using accessibility attributes with given context nodes, selector, and maximum returned node count:

1. If selector does not contain "role" and selector does not contain "name", return error with error code invalid selector.

2. Return the result of collect nodes using accessibility attributes with context nodes, selector, maximum returned node count, and null.

The remote end steps with session and command parameters are:

1. Let navigable id be command parameters["context"].

2. Let navigable be the result of trying to get a navigable with navigable id.

3. Assert: navigable is not null.

4. Let realm be the result of trying to get a realm from a navigable with navigable id of navigable and null.

5. Let locator be command parameters["locator"].

6. If command parameters contains "startNodes", let start nodes parameter be command parameters["startNodes"]. Otherwise let start nodes parameter be null.

7. If command parameters contains "maxNodeCount", let maximum returned node count be command parameters["maxNodeCount"]. Otherwise, let maximum returned node count be null.

8. Let context nodes be an empty list.

9. If start nodes parameter is null, append the document element of navigable’s active document to context nodes. Otherwise, for each serialized start node in start nodes parameter:

   1. Let start node be the result of trying to deserialize shared reference given serialized start node, realm and session.

   2. Append start node to context nodes.

10. Assert size of context nodes is greater than 0.

11. Let type be locator["type"].

12. In the following list of conditions and associated steps, run the first set of steps for which the associated condition is true:

    type is the string "css"

    1. Let selector be locator["value"].

    2. Let result nodes be a result of trying to locate nodes using css given navigable, context nodes, selector and maximum returned nodes.

    type is the string "xpath"

    1. Let selector be locator["value"].

    2. Let result nodes be a result of trying to locate nodes using xpath given navigable, context nodes, selector and maximum returned nodes.

    type is the string "innerText"

    1. Let selector be locator["value"].

    2. If locator contains maxDepth, let max depth be locator["maxDepth"]. Otherwise, let max depth be null.

    3. If locator contains ignoreCase, let ignore case be locator["ignoreCase"]. Otherwise, let ignore case be false.

    4. If locator contains matchType, let match type be locator["matchType"]. Otherwise, let match type be "full".

    5. Let result nodes be a result of trying to locate nodes using inner text given context nodes, selector, max depth, match type, ignore case and maximum returned node count.

    type is the string "accessibility"

    1. Let selector be locator["value"].

    2. Let result nodes be locate nodes using accessibility attributes given context nodes, selector, and maximum returned node count.

13. Assert: maximum returned node count is null or size of result nodes is less than or equal to maximum returned node count.

14. If command parameters contains "serializationOptions", let serialization options be command parameters["serializationOptions"]. Otherwise, let serialization options be a map matching the script.SerializationOptions production with the fields set to their default values.

15. Let result ownership be "none".

16. Let serialized nodes be an empty list.

17. For each result node in result nodes:

    1. Let serialized node be the result of serialize as a remote value with result node, serialization options, result ownership, a new map as serialization internal map, realm and session.

    2. Append serialized node to serialized nodes.

18. Let result be a map matching the browsingContext.LocateNodesResult production, with the nodes field set serialized nodes.

19. Return success with data result.

The remote end steps with session and command parameters are:

1. Let navigable id be the value of the context field of command parameters.

2. Let navigable be the result of trying to get a navigable with navigable id.

3. Assert: navigable is not null.

4. Let wait condition be the value of the wait field of command parameters if present, or "none" otherwise.

5. Let url be the value of the url field of command parameters.

6. Let document be navigable’s active document.

7. Let base be document’s base URL.

8. Let url record be the result of applying the URL parser to url, with base URL base.

9. If url record is failure, return error with error code invalid argument.

10. Let request be a new request whose URL is url record.

11. Return the result of await a navigation with navigable, request and wait condition.

The remote end steps with command parameters are:

1. Let navigable id be the value of the context field of command parameters.

2. Let navigable be the result of trying to get a navigable with navigable id.

3. Assert: navigable is not null.

4. Let ignore cache be the the value of the ignoreCache field of command parameters if present, or false otherwise.

5. Let wait condition be the value of the wait field of command parameters if present, or "none" otherwise.

6. Let document be navigable’s active document.

7. Let url be document’s URL.

8. Let request be a new request whose URL is url.

9. Return the result of await a navigation with navigable, request, wait condition, history handling "reload", and ignore cache ignore cache.

The remote end steps with command parameters are:

1. Let navigable id be the value of the context field of command parameters.

2. Let navigable be the result of trying to get a navigable with navigable id.

3. If navigable is not a top-level traversable, return error with error code invalid argument.

4. If the implementation is unable to adjust the navigable’s layout viewport parameters with the given command parameters for any reason, return error with error code unsupported operation.

5. If command parameters contains the viewport field:

   1. Let viewport be the command parameters["viewport"].

   2. If viewport is not null, set the width of navigable’s layout viewport to be the width of viewport in CSS pixels and set the height of the navigable’s layout viewport to be the height of viewport in CSS pixels.

   3. Otherwise, set the navigable’s layout viewport to the implementation-defined default.

6. Run the CSSOM View § 13.1 Resizing viewports steps.

7. If command parameters contains the devicePixelRatio field:

   1. Let device pixel ratio be the command parameters["devicePixelRatio"].

   2. For the navigable and all descendant navigables:

      1. Let navigable be the navigable whose active document is navigable’s active document.

      2. If device pixel ratio is not null:

         1. When the select an image source from a source set are run, act as if the implementation’s pixel density was set to device pixel ratio when selecting an image.

         2. For the purposes of the resolution media feature, act as if the implementation’s resolution is device pixel ratio dppx scaled by the page zoom.

         3. Set device pixel ratio overrides[navigable] to device pixel ratio.

            Note: This will take an effect because of the patch of § 8.3.1 Determine the device pixel ratio.

      3. Otherwise:

         1. When the select an image source from a source set steps are run, use the implementation’s default behavior, without any changes made by previous invocations of these steps.

         2. For the purposes of the resolution media feature, use the implementation’s default behavior, without any changes made by previous invocations of these steps.

         3. Remove navigable from device pixel ratio overrides.

      4. Run evaluate media queries and report changes for document currently loaded in a specified navigable.

8. Return success with data null.

The remote end steps with command parameters are:

1. Let navigable be the result of trying to get a navigable with command parameters["context"].

2. If navigable is not a top-level traversable, return error with error code invalid argument.

3. Assert: navigable is not null.

4. Let delta be command parameters["delta"].

5. Let resume id be a unique string.

6. Queue a task on navigable’s session history traversal queue to run the following steps:

   1. Let all steps be the result of getting all used history steps for navigable.

   2. Let current index be the index of navigable’s current session history step within all steps.

   3. Let target index be current index plus delta.

   4. Let valid entry be false if all steps[target index] does not exist, or true otherwise.

   5. Resume with "check history", resume id, and valid entry.

7. Let is valid entry be await with «"check history"», and resume id.

8. If is valid entry is false, return error with error code no such history entry.

9. Traverse the history by a delta given delta and navigable.

   There is a race condition in the algorithm as written because by the time we try to navigate the target session history entry might not exist. Once we support waiting for history to navigate we can handle this more robustly.

10. TODO: Support waiting for the history traversal to complete.

11. Let body be a map matching the browsingContext.TraverseHistoryResult production.

12. Return success with data body.

The WebDriver BiDi page show steps given context and navigation status are:

Do we want to expose a `browsingContext.pageShow event? In that case we’d need to call this whenever `pageshow` is going to be emitted, not just on bfcache restore, and also add the persisted status to the data.

1. Let navigation id be navigation status’s id.

2. Resume with "page show", navigation id, and navigation status.

The WebDriver BiDi pop state steps given context and navigation status are:

1. Let navigation id be navigation status’s id.

2. Resume with "pop state", navigation id, and navigation status.

To Recursively emit context created events given session and navigable:

1. Emit a context created event with session and navigable.

2. For each child navigable, child, of navigable:

   1. Recursively emit context created events given session and child.

To Emit a context created event given session and navigable:

1. Let params be the result of get the navigable info given navigable, 0, and true.

2. Let body be a map matching the browsingContext.ContextCreated production, with the params field set to params.

3. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi navigable created steps given navigable and opener navigable:

1. Set navigable’s original opener to opener navigable, if opener navigable is provided.

2. If the navigable cache behavior with navigable is "bypass", then perform implementation-defined steps to disable any implementation-specific resource caches for network requests originating from navigable.

3. Let related navigables be a set containing navigable.

4. For each session in the set of sessions for which an event is enabled given "browsingContext.contextCreated" and related navigables:

   1. Emit a context created event given session and navigable.

The remote end subscribe steps, with subscribe priority 1, given session, navigables and include global are:

1. For each navigable in navigables:

   1. Recursively emit context created events given session and navigable.

The remote end event trigger is the WebDriver BiDi navigable destroyed steps given navigable:

1. Let params be the result of get the navigable info, given navigable, null, and true.

2. Let body be a map matching the browsingContext.ContextDestroyed production, with the params field set to params.

3. Let related navigables be a set containing the result of get the parent navigable with navigable, if that is not null, or an empty set otherwise.

4. For each session in the set of sessions for which an event is enabled given "browsingContext.contextDestroyed" and related navigables:

   1. Emit an event with session and body.

It’s unclear if we ought to only fire this event for browsing contexts that have active documents; navigation can also cause contexts to become inaccessible but not yet get discarded because bfcache.

The remote end event trigger is the WebDriver BiDi navigation started steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.NavigationStarted production, with the params field set to params.

3. Let navigation id be navigation status’s id.

4. Let related navigables be a set containing navigable.

5. Resume with "navigation started", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.navigationStarted" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi fragment navigated steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.FragmentNavigated production, with the params field set to params.

3. Let navigation id be navigation status’s id.

4. Let related navigable be a set containing navigable.

5. Resume with "fragment navigated", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.fragmentNavigated" and related navigable:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi history updated steps given navigable:

1. Let url be the result of running the URL serializer, given navigable’s active browsing context's active document's URL.

2. Let params be a map matching the browsingContext.HistoryUpdatedParameters production, with the url field set to url and the context field set to navigable’s navigable id.

3. Let body be a map matching the browsingContext.HistoryUpdated production, with the params field set to params.

4. Let related browsing contexts be a set containing navigable’s active browsing context.

5. For each session in the set of sessions for which an event is enabled given "browsingContext.historyUpdated" and related browsing contexts:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi DOM content loaded steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.DomContentLoaded production, with the params field set to params.

3. Let related navigables be a set containing navigable.

4. Let navigation id be navigation status’s id.

5. Resume with "domContentLoaded", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.domContentLoaded" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi load complete steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.Load production, with the params field set to params.

3. Let related navigables be a set containing navigable.

4. Let navigation id be navigation status’s id.

5. Resume with "load", navigation id and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.load" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi download started steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.DownloadWillBegin production, with the params field set to params.

3. Let navigation id be navigation status’s id.

4. Let related navigables be a set containing navigable.

5. Resume with "download started", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.downloadWillBegin" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi navigation aborted steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.NavigationAborted production, with the params field set to params.

3. Let navigation id be navigation status’s id.

4. Let related navigables be a set containing navigable.

5. Resume with "navigation aborted", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.navigationAborted" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi navigation failed steps given navigable and navigation status:

1. Let params be the result of get the navigation info given navigable and navigation status.

2. Let body be a map matching the browsingContext.NavigationFailed production, with the params field set to params.

3. Let navigation id be navigation status’s id.

4. Let related navigables be a set containing navigable.

5. Resume with "navigation failed", navigation id, and navigation status.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.navigationFailed" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi user prompt closed steps given window, type, accepted and optional user text (default: null).

1. Let navigable be window’s navigable.

2. Let navigable id be the navigable id for navigable.

3. Let params be a map matching the browsingContext.UserPromptClosedParameters production with the context field set to navigable id, the accepted field set to accepted, the type field set to type, and the userText field set to user text if user text is not null or omitted otherwise.

4. Let body be a map matching the BrowsingContextUserPromptClosedEvent production, with the params field set to params.

5. Let related navigables be a set containing navigable.

6. For each session in the set of sessions for which an event is enabled given "browsingContext.userPromptClosed" and related navigables:

   1. Emit an event with session and body.

The remote end event trigger is the WebDriver BiDi user prompt opened steps given window, type, message, and optional default value (default: null).

1. Let navigable be window’s navigable.

2. Let navigable id be the navigable id for navigable.

3. Let handler configuration be get the prompt handler with type.

4. Let handler be handler configuration’s handler.

5. Let params be a map matching the browsingContext.UserPromptOpenedParameters production with the context field set to navigable id, the type field set to type, the message field set to message, the defaultValue field set to default value if default value is not null or omitted otherwise, and the handler field set to handler.

6. Let body be a map matching the browsingContext.UserPromptOpened production, with the params field set to params.

7. Let related navigables be a set containing navigable.

8. For each session in the set of sessions for which an event is enabled given "browsingContext.userPromptOpened" and related navigables:

   1. Emit an event with session and body.

9. If handler is "ignore", set handler to "none".

10. Return handler.

NetworkCommand = (
  network.AddIntercept //
  network.ContinueRequest //
  network.ContinueResponse //
  network.ContinueWithAuth //
  network.FailRequest //
  network.ProvideResponse //
  network.RemoveIntercept //
  network.SetCacheBehavior
)

NetworkResult = (
   network.AddInterceptResult
)

NetworkEvent = (
    network.AuthRequired //
    network.BeforeRequestSent //
    network.FetchError //
    network.ResponseCompleted //
    network.ResponseStarted
)

To get the network intercepts given session, event, request, and navigable id:

1. Let session intercepts be session’s intercept map.

2. Let intercepts be an empty list.

3. Run the steps under the first matching condition:

   event is "network.beforeRequestSent"

   Set phase to "beforeRequestSent".

   event is "network.responseStarted"

   Set phase to "responseStarted".

   event is "network.authRequired"

   Set phase to "authRequired".

   event is "network.responseCompleted"

   Return intercepts.

4. Let url be the result of running the URL serializer with request’s URL.

5. For each intercept id → intercept of session intercepts:

   1. If intercept’s contexts is not null:

      1. If intercept’s contexts does not contain navigable id:

         1. Continue.

   2. If intercept’s phases contains phase:

      1. Let url patterns be intercept’s url patterns.

      2. If url patterns is empty:

         1. Append intercept id to intercepts.

         2. Continue.

      3. For each url pattern in url patterns:

         1. If match URL pattern with url pattern and url:

            1. Append intercept id to intercepts.

            2. Break.

6. Return intercepts.

To update the response given session, command and command parameters:

1. Let blocked requests be session’s blocked request map.

2. Let request id be command parameters["request"].

3. If blocked requests does not contain request id then return error with error code no such request.

4. Let (request, phase, response) be blocked requests[request id].

5. If phase is "beforeRequestSent" and command is "continueResponse", return error with error code "invalid argument".

   TODO: Consider a different error

6. If response is null:

   1. Assert: phase is "beforeRequestSent".

   2. Set response to a new response.

7. If command parameters contains "statusCode":

   1. Set responses’s status be command parameters["statusCode"].

8. If command parameters contains "reasonPhrase":

   1. Set responses’s status message be UTF-8 encode with command parameters["reasonPhrase"].

9. If command parameters contains "headers":

   1. Let headers be an empty header list.

   2. For header in command parameters["headers"]:

      1. Let deserialized header be deserialize header with header.

      2. If deserialized header’s name does not match the field-name token production, return error with error code "invalid argument".

      3. If deserialized header’s value does not match the header value production, return error with error code "invalid argument".

      4. Append deserialized header to headers.

   3. Set response’s header list to headers.

10. If command parameters contains "cookies":

    1. If command parameters contains "headers", let headers be response’s header list.

       Otherwise:

       1. Let headers be an empty header list.

       2. For each header in response’s headers list:

          1. Let name be header’s name.

          2. If byte-lowercase name is not `set-cookie`:

             1. Append header to headers

    2. For cookie in command parameters["cookies"]:

       1. Let header value be serialize set-cookie header with cookie.

       2. Append (`Set-Cookie`, header value) to headers.

       3. Set response’s header list to headers.

11. If command parameters contains "credentials":

    This doesn’t have a way to cancel the auth.

    1. Let credentials be command parameters["credentials"].

    2. Assert: credentials["type"] is "password".

    3. Set response’s authentication credentials to (credentials["username"], credentials["password"])

12. Return response

network.AuthChallenge = {
  scheme: text,
  realm: text,
}

To extract challenges given response:

Should we include parameters other than realm?

1. If response’s status is 401, let header name be `WWW-Authenticate`. Otherwise if response’s status is 407, let header name be `Proxy-Authenticate`. Otherwise return null.

2. Let challenges be a new list.

3. For each (name, value) in response’s header list:

   as in Fetch it’s unclear if this is the right way to handle multiple headers, parsing issues, etc.

   1. If name is a byte-case-insensitive match for header name:

      1. Let header challenges be the result of parsing value into a list of challenges, each consisting of a scheme and a list of parameters, each of which is a tuple (name, value), according to the rules of [RFC9110].

      2. For each header challenge in header challenges:

         1. Let scheme be header challenge’s scheme.

         2. Let realm be the empty string.

         3. For each (param name, param value) in header challenge’s parameters:

            1. If param name equals `realm` let realm be UTF-8 decode param value.

         4. Let challenge be a new map matching the network.AuthChallenge production, with the scheme field set to scheme and the realm field set to realm.

      3. Append challenge to challenges.

4. Return challenges.

network.AuthCredentials = {
  type: "password",
  username: text,
  password: text,
}

network.BaseParameters = (
    context: browsingContext.BrowsingContext / null,
    isBlocked: bool,
    navigation: browsingContext.Navigation / null,
    redirectCount: js-uint,
    request: network.RequestData,
    timestamp: js-uint,
    ? intercepts: [+network.Intercept]
)

To process a network event given session, event, and request:

1. Let request data be the result of get the request data with request.

2. Let navigation be request’s navigation id.

3. Let navigable id be null.

4. Let top-level navigable id be null.

5. If request’s window is an environment settings object:

   1. Let environment settings be request’s window

   2. If there is a navigable whose active window is environment settings’ global object, set navigable id to the navigable id for that navigable, and set top-level navigable id to be top-level traversable's navigable id for that context.

6. Let intercepts be the result of get the network intercepts with session, event, request, and top-level navigable id.

7. Let redirect count be request’s redirect count.

8. Let timestamp be a time value representing the current date and time in UTC.

9. If intercepts is not empty, let is blocked be true, otherwise let is blocked be false.

10. Let params be map matching the network.BaseParameters production, with the request field set to request data, the navigation field set to navigation, the context field set to navigable id, the timestamp field set to timestamp, the redirectCount field set to redirect count, the isBlocked field set to is blocked, and intercepts field set to intercepts if is blocked is true, or omitted otherwise.

11. Return params

network.BytesValue = network.StringValue / network.Base64Value;

network.StringValue = {
  type: "string",
  value: text,
}

network.Base64Value = {
  type: "base64",
  value: text,
}

To deserialize protocol bytes given protocol bytes:

Note: this takes bytes encoded as a network.BytesValue and returns a byte sequence.

1. If protocol bytes matches the network.StringValue production, let bytes be UTF-8 encode protocol bytes["value"].

2. Otherwise if protocol bytes matches the network.Base64Value production. Let bytes be forgiving-base64 decode protocol bytes["value"].

3. Return bytes.

To serialize protocol bytes given bytes:

Note: this takes a byte sequence and returns a network.BytesValue.

1. Let text be UTF-8 decode without BOM or fail bytes.

2. If text is failure, return a map matching the network.Base64Value production, with value set to forgiving-base64 encode bytes.

3. Return a map matching the network.StringValue production, with value set to text.

network.SameSite = "strict" / "lax" / "none"

network.Cookie = {
    name: text,
    value: network.BytesValue,
    domain: text,
    path: text,
    size: js-uint,
    httpOnly: bool,
    secure: bool,
    sameSite: network.SameSite,
    ? expiry: js-uint,
    Extensible,
};

To serialize cookie given stored cookie:

Note: The definitions of stored cookie’s fields are from [COOKIES], except samesite-flag, which is from [SAME-SITE-COOKIES].

1. Let name be the result of UTF-8 decode with stored cookie’s name field.

2. Let value be serialize protocol bytes with stored cookie’s value.

3. Let domain be stored cookie’s domain field.

4. Let path be stored cookie’s path field.

5. Let expiry be stored cookie’s expiry-time field represented as a unix timestamp, if set, or null otherwise.

6. Let size be the byte length of the result of serializing stored cookie as it would be represented in a Cookie header.

7. Let http only be true if stored cookie’s http-only-flag is true, or false otherwise.

8. Let secure be true if stored cookie’s secure-only-flag is true, or false otherwise.

9. Let same site be "none" if stored cookie’s samesite-flag is "None", "lax" if it is "Lax", or "strict" if it is "Strict".

10. Return a map matching the network.Cookie production, with the name field set to name, the value field set to value, the domain field set to domain, the path field set to path, the expiry field set to expiry if it’s not null, or omitted otherwise, the size field set to size, the httpOnly field set to http only, the secure field set to secure, and the sameSite field set to same site.

network.CookieHeader = {
    name: text,
    value: network.BytesValue,
};

To serialize cookie header given protocol cookie:

1. Let name be UTF-8 encode protocol cookie["name"].

2. Let value be deserialize protocol bytes with protocol cookie["value"].

3. Let header value be the byte sequence formed by concatenating name, `=`, and value

4. Return header value.

network.FetchTimingInfo = {
    timeOrigin: float,
    requestTime: float,
    redirectStart: float,
    redirectEnd: float,
    fetchStart: float,
    dnsStart: float,
    dnsEnd: float,
    connectStart: float,
    connectEnd: float,
    tlsStart: float,
    requestStart: float,
    responseStart: float,
    responseEnd: float,
};

To get the fetch timings given request:

1. Let global be request’s client.

2. If global is null, return a map matching the network.FetchTimingInfo production, with all fields set to 0.

3. Let time origin be get time origin timestamp with global.

4. Let timings be request’s fetch timing info.

5. Let connection timing be timings’ final connection timing info if it’s not null, or a new connection timing info otherwise.

6. Let request time be convert fetch timestamp given timings’ start time and global.

7. Let redirect start be convert fetch timestamp given timings’ redirect start time and global.

8. Let redirect end be convert fetch timestamp given timings’ redirect end time and global.

9. Let fetch start be convert fetch timestamp given timings’ post-redirect start time and global.

10. Let DNS start be convert fetch timestamp given connection timing’s domain lookup start time and global.

11. Let DNS end be convert fetch timestamp given connection timing’s domain lookup end time and global.

12. Let TLS start be convert fetch timestamp given connection timing’s secure connection start time and global.

13. Let connect start be convert fetch timestamp given connection timing’s connection start time and global.

14. Let connect end be convert fetch timestamp given connection timing’s connection end time and global.

15. Let request start be convert fetch timestamp given timings’ final network-request start time and global.

16. Let response start be convert fetch timestamp given timings’ final network-response start time and global.

17. Let response end be convert fetch timestamp given timings’ end time and global.

18. Return a map matching the network.FetchTimingInfo production with the timeOrigin field set to time origin, the requestTime field set to request time, the redirectStart field set to redirect start, the redirectEnd field set to redirect end, the fetchStart field set to fetch start, the dnsStart field set to DNS start, the dnsEnd field set to DNS end, the connectStart field set to connect start, the connectEnd field set to connect end, the tlsStart field set to TLS start, the requestStart field set to request start, the responseStart field set to response start, and the responseEnd field set to response end.

network.Header = {
  name: text,
  value: network.BytesValue,
}

To serialize header given name bytes and value bytes:

1. Let name be the result of UTF-8 decode with name bytes.

   Assert: Since header names are constrained to be ASCII-only this cannot fail.

2. Let value be serialize protocol bytes with value bytes.

3. Return a map matching the network.Header production, with the name field set to name, and the value field set to value.

To deserialize header given protocol header:

1. Let name be UTF-8 encode protocol header["name"].

2. Let value be deserialize protocol bytes with protocol header["value"].

3. Return a header (name, value).

network.Initiator = {
    ? columnNumber: js-uint,
    ? lineNumber: js-uint,
    ? request: network.Request,
    ? stackTrace: script.StackTrace,
    ? type: "parser" / "script" / "preflight" / "other"
};

To get the initiator given request:

1. If request’s initiator type is "fetch" or "xmlhttprequest":

   1. Let stack trace be the current stack trace.

   2. If stack trace has size of 1 or greater, let line number be value of the lineNumber field in stack trace[0], and let column number be the value of the columnNumber field in stack trace[0]. Otherwise let line number and column number be 0.

   Otherwise, let stack trace, column number, and line number all be null.

   TODO: Chrome includes the current parser position as column number / line number for parser-inserted resources.

2. Return a map matching the network.Initiator production, the columnNumber field set to column number if it’s not null, or omitted otherwise, the lineNumber field set to line number if it’s not null, or omitted otherwise and the stackTrace field set to stack trace if it’s not null, or omitted otherwise.

network.Intercept = text

network.Request = text;

network.RequestData = {
    request: network.Request,
    url: text,
    method: text,
    headers: [*network.Header],
    cookies: [*network.Cookie],
    headersSize: js-uint,
    bodySize: js-uint / null,
    destination: text,
    initiatorType: text / null,
    timings: network.FetchTimingInfo,
};

To get the request data given request:

1. Let request id be request’s request id.

2. Let url be the result of running the URL serializer with request’s URL.

3. Let method be request’s method.

4. Let body size be null.

5. Let body be request’s body.

6. If body is a byte sequence, set body size to the length of that sequence. Otherwise, if body is a body then set body size to that body’s length.

7. Let headers size be the size in bytes of request’s headers list when serialized as mandated by [HTTP11].

   Note: For protocols which allow header compression, this is the compressed size of the headers, as sent over the network.

8. Let headers be an empty list.

9. Let cookies be an empty list.

10. For each (name, value) in request’s headers list:

    1. Append the result of serialize header with name and value to headers.

    2. If name is a byte-case-insensitive match for "Cookie" then:

       1. For each cookie in the user agent’s cookie store that are included in request:

          Note: [COOKIES] defines some baseline requirements for which cookies in the store can be included in a request, but user agents are free to impose additional constraints.

          1. Append the result of serialize cookie given cookie to cookies.

11. Let destination be request’s destination.

12. Let initiator type be request’s initiator type.

13. Let timings be get the fetch timings with request.

14. Return a map matching the network.RequestData production, with the request field set to request id, url field set to url, the method field set to method, the headers field set to headers, the cookies field set to cookies, the headersSize field set to headers size, the bodySize field set to body size, the destination field set to destination, the initiatorType field set to initiator type, and the timings field set to timings.

network.ResponseContent = {
    size: js-uint
};

To get the response content info given response.

1. Return a new map matching the network.ResponseContent production, with the size field set to response’s response body info's decoded size

network.ResponseData = {
    url: text,
    protocol: text,
    status: js-uint,
    statusText: text,
    fromCache: bool,
    headers: [*network.Header],
    mimeType: text,
    bytesReceived: js-uint,
    headersSize: js-uint / null,
    bodySize: js-uint / null,
    content: network.ResponseContent,
    ?authChallenges: [*network.AuthChallenge],
};

To get the protocol given response:

1. Let protocol be the empty string.

2. If response’s final connection timing info is not null, set protocol to response’s final connection timing info's ALPN negotiated protocol.

3. If protocol is the empty string, or is equal to "unknown":

   1. Set protocol to response’s url's scheme

   2. If protocol is equal to either "http" or "https" and response has an associated HTTP Response.

      Note: [FETCH] isn’t clear about the relation between a HTTP network response and a response object.

      1. Let http version be the HTTP Response’s Status line’s HTTP-version [HTTP11].

      2. If http version starts with "HTTP/":

         1. Let version be the code unit substring of http version from 5 to http version’s length.

         2. If version is "0.9", set protocol to "http/0.9", otherwise if version is "1.0", set protocol to "http/1.0", otherwise if version is "1.1", set protocol to "http/1.1".

4. Return protocol.

To get the response data given response:

1. Let url be the result of running the URL serializer with response’s URL.

2. Set protocol to get the protocol given response.

3. Let status be response’s status.

4. Let status text be response’s status message.

5. If response’s cache state is "local", let from cache be true, otherwise let it be false.

6. Let headers be an empty list.

7. Let mime type be the essence of the computed mime type for response.

   Note: this is whatever MIME type the browser is actually using, even if it isn’t following the exact algorithm in the [MIMESNIFF] specification.

8. For each (name, value) in response’s headers list:

   1. Append the result of serialize header with name and value to headers.

9. Let bytes received be the total number of bytes transmitted as part of the HTTP response associated with response.

10. Let headers size be the number of bytes transmitted as part of the header fields section of the HTTP response.

11. Let body size be response’s response body info's encoded size.

12. Let content be the result of get the response content info with response.

13. Let auth challenges be the result of extract challenges with response.

14. Return a map matching the network.ResponseData production, with the url field set to url, the protocol field set to protocol, the status field set to status, the statusText field set to status text, the fromCache field set to from cache, the headers field set to headers, the mimeType field set to mime type, the bytesReceived field set to bytes received, the headersSize field set to headers size, the bodySize field set to body size, content field set to content, and the authChallenges field set to auth challenges if it’s not null, or omitted otherwise.

network.SetCookieHeader = {
    name: text,
    value: network.BytesValue,
    ? domain: text,
    ? httpOnly: bool,
    ? expiry: text,
    ? maxAge: js-int,
    ? path: text,
    ? sameSite: network.SameSite,
    ? secure: bool,
}

To serialize an integer given input that is an integer:

Note: This produces the shortest representation of input as a string of decimal digits.

1. Let serialized be an empty string.

2. Let value be input.

3. While value is greater than 0:

   1. Let x be value divided by 10.

   2. Let most significant digits be the integer part of x.

   3. Let y be most significant digits multiplied by 10.

   4. Let least significant digit be value - y.

   5. Assert: least significant digit is an integer in the range 0 to 9, inclusive.

   6. Let codepoint be the code point whose value is U+0030 DIGIT ZERO’s value + least significant digit.

   7. Prepend codepoint to serialized.

   8. Set value to most significant digits.

4. Return serialized.

To serialize set-cookie header given protocol cookie:

1. Let name be UTF-8 encode protocol cookie["name"].

2. Let value be deserialize protocol bytes with protocol cookie["value"].

3. Let header value be the byte sequence formed by concatenating name, `=`, and value.

4. If protocol cookie contains "expiry":

   1. Let attribute be `;Expires=`

   2. Append UTF-8 encode protocol cookie["expiry"] to attribute.

   3. Append attribute to header value.

5. If protocol cookie contains "maxAge":

   1. Let attribute be `;Max-Age=`

   2. Let max age string be serialize an integer protocol cookie["maxAge"].

   3. Append UTF-8 encode max age string to attribute.

   4. Append attribute to header value.

6. If protocol cookie contains "domain":

   1. Let attribute be `;Domain=`

   2. Append UTF-8 encode protocol cookie["domain"] to attribute.

   3. Append attribute to header value.

7. If protocol cookie contains "path":

   1. Let attribute be `;Path=`

   2. Append UTF-8 encode protocol cookie["path"] to attribute.

   3. Append attribute to header value.

8. If protocol cookie contains "secure" and protocol cookie["secure"] is true:

   1. Append `;Secure` to header value.

9. If protocol cookie contains "httpOnly" and protocol cookie["httpOnly"] is true:

   1. Append `;HttpOnly` to header value.

10. If protocol cookie contains "sameSite":

    1. Let attribute be `;SameSite=`

    2. Append UTF-8 encode protocol cookie["sameSite"] to attribute.

    3. Append attribute to header value.

11. Return header value.

network.UrlPattern = (
  network.UrlPatternPattern /
  network.UrlPatternString
)

network.UrlPatternPattern = {
    type: "pattern",
    ?protocol: text,
    ?hostname: text,
    ?port: text,
    ?pathname: text,
    ?search: text,
}


network.UrlPatternString = {
    type: "string",
    pattern: text,
}

To unescape URL pattern given pattern

1. Let forbidden characters be the set of codepoints «U+0028 ((), U+0029 ()), U+002A (*), U+007B ({), U+007D (})»

2. Let result be the empty string.

3. Let is escaped character be false.

4. For each codepoint in pattern:

   1. If is escaped character is false:

      1. If forbidden characters contains codepoint, return error with error code invalid argument.

      2. If codepoint is U+005C (\):

         1. Set is escaped character to true.

         2. Continue.

   2. Append codepoint to result.

   3. Set is escaped character to false.

5. Return success with data result.