I have been trying to do this too since I have my internal customers who would like to have their CEF apps driven with the existing Selenium wrapper code we already have.
I see that the cefclient application works fine with devtools as long as I specify the debugger port. I could then browse to localhost:port and use the devtools UI againt the CEF loaded session.
On the other side of the wire: the chromedriver devs indicated that with some changes to chromedriver locally to point to cef instead of chrome, we could potentially drive CEF with chromedriver that is being built with devtools support now. I have been chatting with the chromedriver folks at this thread about this:
https://groups.google.com/d/topic/chrom ... discussionI am getting setup to build chromedriver locally, now that I can build CEF3 cefclient application locally that I am using as the target app for driving. Any thoughts on the feasibility of this approach? Is a CEF3 app basically already loaded with devtools support?
Thanks!