Inspectable WebContents via Puppeteer Remote Debugging

[pit...@gmail.com]

Hello,

I'm trying to automated an application that is using CEF. I am able to use Puppeteer to connect to the application via localhost + port. What actually shows upon loading is a text "Inspectable WebContents" along with an hyperlink that leads to an inspector page.

While trying to automate this, I noticed the DOM that was actually loading after clicking on the hyperlink was the front-end devtools and not the webpage from the application. Has anyone else encountered this?

[Joel Griffith]

This is actually expected behavior and is how the remote debugger works (which is the HTML you’re encountering).

I maintain a Docker image that connects puppeteer in a similar fashion, feel free to use it directly or take it as “inspiration” for how to connect a remote Chrome instance. Repo is located here: https://github.com/joelgriffith/browserless

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/7ac7bda7-d954-4adf-82a9-a48e96c2d548%40chromium.org.