Skip to content

Commit 1e08d83

Browse files
committed
2 parents ef7aadd + cfad292 commit 1e08d83

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

README.md

+14-1
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,19 @@
33
# ChromeDevTools
44
C# Library to interact with the Chrome Developer Tools.
55

6+
```c#
7+
chromeSession.Subscribe<Protocol.Page.DomContentEventFiredEvent>((o, e) =>
8+
{
9+
var domContentEvent = (Event<DomContentEventFiredEvent>)e;
10+
Console.WriteLine("DomContentEvent: " + domContentEvent.Params.Timestamp);
11+
});
12+
13+
chromeSession.SendAsync(new NavigateCommand
14+
{
15+
Url = "http://www.google.com"
16+
}).Wait();
17+
```
18+
619
## About
720
This library is C# API that enabled interaction with the Chrome Developer Tools. When the Chrome Developer Tools are started, the chrome process starts a server. The Chrome Developer Tools UI communicates with this server via Web Sockets. So can you. In fact, everything in the Chrome Developers Tools UI is available to you via JSON, by default. This library makes it available to you in C#.
821

@@ -55,4 +68,4 @@ If you didn't read the entire README (I don't blame you, I wouldn't), I've inclu
5568
* Here's what the Chrome Team has to say about the Developer Tools protocol (it's not much)
5669
* [https://developer.chrome.com/devtools/docs/debugger-protocol](https://developer.chrome.com/devtools/docs/debugger-protocol)
5770
* Some cool apps that other developers have built using the Chrome Debugging Protocol
58-
* [https://developer.chrome.com/devtools/docs/debugging-clients](https://developer.chrome.com/devtools/docs/debugging-clients)
71+
* [https://developer.chrome.com/devtools/docs/debugging-clients](https://developer.chrome.com/devtools/docs/debugging-clients)

0 commit comments

Comments
 (0)