Helper to easily obtain a response and its body

[mvdan]

We added ExampleRetrieveHTML, which did this with network.GetResponseBody and a dozen lines of Go code, but apparently it's not that simple. We also need to wait for network.EventLoadingFinished on top of the response's network.EventResponseReceived.

At this rate, the user would probably need over twenty lines of non-trivial Go code. This probably calls for a simple helper to deal with the simple use cases.

[marcelloh]

Perhaps, I'mn a nitwit for these solutions, but how can the document title be retrieved in the easy way that you have now, and a full source only with a dozen lines of code? How come that fill html source needs a EventResponseReceived kind of solution, while Title is just Title (I never looked what it does under the hood). I can imagine, the source needs to be in memory to have access to the title. But as I said: I'm the nitwit here ;-)

[marcelloh]

Btw. Now I did some extra digging. Title is evaluated like a javascript command. so I was looking if there is such a thing for all of the html. I found document.all to contain that information.
When I do document.all[0] or document.all[0].innerHTML I get more info in the console. Perhaps this is usable?

[mvdan]

We already have InnerHTML and OuterHTML as actions you can use. This is different from obtaining the original HTML response sent by the HTTP server, though. That requires waiting for a couple of events and executing an action, so it's not as simple.

[kenshaw]

This is doable, but the there's a reason that Chrome/ium does a secondary retrieval when doing view-source:. Will make a point of implementing this along with HAR capture ability.

[marco-m]

For people coming here and wondering where ExampleRetrieveHTML() is, it has been renamed to Example_retrieveHTML() in e657155 and is in file chromedp/example_test.go. It is also visible in the godoc: https://godoc.org/github.com/chromedp/chromedp#example-package--RetrieveHTML

[ianmarmour]

Would love to see this feature added having to create a listener and capture the response body is more painful then it needs to be for any XML or JSON requests this would be preferable