Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions protocol
Original file line number Diff line number Diff line change
Expand Up @@ -547,6 +547,26 @@ This indicates that the tab has begun navigating to <i>newURL</i>; JavaScript ex

where <i>newURL</i> and <i>newTitle</i> are the URL and title of the page the tab is now showing. The <i>tabThreadActor</i> given in the response to the original <code>"attach"</code> packet is now debugging the new page's code.

To reload the tab, a client sends a message of the form:

{ "to":<i>tabActor</i>, "type":"reload" }

to which the tab actor simply replies:

{ "from":<i>tabActor</i> }

The server will send <i>tabNavigated</i> notifications after the response packet, as the navigation takes place.

To navigate the tab to another page, a client sends a message of the form:

{ "to":<i>tabActor</i>, "type":"navigateTo", "url":<i>url</i> }

where <i>url</i> is the URL of the page to navigate to. The tab actor simply replies:

{ "from":<i>tabActor</i> }

The server will also send <i>tabNavigated</i> notifications after the response packet, as the navigation takes place.

If the user closes a tab to which the client is attached, its <i>tabActor</i> sends a notification packet of the form:

{ "from":<i>tabActor</i>, "type":"tabDetached" }
Expand Down