0e92de5e65
The Default folder is created asynchronously to Chrome starting to listen on the debugging protocol port. So we can't expect it to exist. Instead, base the example on DevToolsActivePort, which we can rely on. |
||
|---|---|---|
| _example | ||
| .github | ||
| kb | ||
| testdata | ||
| .gitignore | ||
| .travis.yml | ||
| actions.go | ||
| allocate_test.go | ||
| allocate.go | ||
| browser.go | ||
| chromedp_test.go | ||
| conn.go | ||
| context.go | ||
| errors.go | ||
| eval.go | ||
| example_test.go | ||
| go.mod | ||
| go.sum | ||
| handler.go | ||
| input_test.go | ||
| input.go | ||
| js.go | ||
| LICENSE | ||
| nav_test.go | ||
| nav.go | ||
| query_test.go | ||
| query.go | ||
| README.md | ||
| sel_test.go | ||
| sel.go | ||
| util.go | ||
About chromedp 
Package chromedp is a faster, simpler way to drive browsers supporting the Chrome DevTools Protocol in Go using the without external dependencies (ie, Selenium, PhantomJS, etc).
Installing
Install in the usual Go way:
go get -u github.com/chromedp/chromedp
Examples
Please see the examples project for more examples. Please refer to the GoDoc API listing for a summary of the API and Actions.
Resources
- chromedp: A New Way to Drive the Web - GopherCon SG 2017 talk
- Chrome DevTools Protocol - Chrome DevTools Protocol Domain documentation
- chromedp examples - various
chromedpexamples github.com/chromedp/cdproto- GoDoc listing for the CDP domains used bychromedpgithub.com/chromedp/cdproto-gen- tool used to generatecdprotogithub.com/chromedp/chromedp-proxy- a simple CDP proxy for logging CDP clients and browsers
TODO
- Move timeouts to context (defaults)
- Implement more query selector options (allow over riding context timeouts)
- Contextual actions for "dry run" (or via an accumulator?)
- Network loader / manager
- Profiler