Consider integrating Chrome DevTools protocol about gowitness HOT 7 CLOSED

Exploring more avenues for taking screenshots would absolutely be awesome! Lets experiment :)

from gowitness.

Great! FWIW, I was able to prototype my use case (auto-capture screenshot of execution trace during a CI/CD pipeline) in about 15 minutes. Relevant code at https://github.com/hamiltont/trace-grok/blob/master/harness.go#L121 shows that IMO it's really easy to use this chromedp project. The project documentation is really good. It does require the google-chrome binary to be available on the PATH (not sure if gowitness requires that already)

The added power of this tool would also allow a lot of new capabilities. In addition to my requested capability (a timer that only starts when the page is rendered), we could add support for partial screenshots (e..g --screenshot-id "#sidebar" --screenshot-query "body > overlay .buynow" --screenshot-frame <some frame id>) which is kind of neat.

from gowitness.

Going to experiment with using chromedp in gowitness and will let you know how it goes, hopefully it'll clear up the blank screenshot issues we run across

from gowitness.

@randomactsofsecurity awesome! Please feel free to reuse any code of mine in your attempt, I've no claim to it, just never got around to making a proper PR

from gowitness.

Hah! @randomactsofsecurity I have ported the screenshot logic to use chromedp this week and it seems to work fine. I am actually busy refactoring large parts of the code for what might end up being v2 of gowitness. Should see some commits land soon™

from gowitness.

Sweet sounds great, looking forward to testing it out!

from gowitness.

V2 just landed using chromedp!

from gowitness.