Closed GoogleCodeExporter closed 9 years ago
I assume this would be configurable, we would not want our users to have access
to it in a production build of our app.
Original comment by custa1...@gmail.com
on 28 Apr 2012 at 3:54
@comment#1: Correct, it will be configurable.
Original comment by magreenb...@gmail.com
on 29 Apr 2012 at 3:01
I would like to know if somebody has started working already on this issue.
If so, I’d like to get in contact to find out the progress and possibly
discuss the opportunity to contribute to this work.
If no one has started work on it yet, any information, help, hints, tips, etc.
are welcome.
Original comment by m...@telfort.nl
on 7 Nov 2012 at 2:54
I'm not aware of anyone working on this currently. See
DevToolsWindow::InspectElement as a starting place for understanding the Chrome
implementation:
http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/browser/debugger/devto
ols_window.cc&exact_package=chromium&q=InspectElement&type=cs&l=173
Original comment by magreenb...@gmail.com
on 8 Nov 2012 at 4:15
Any news on this ?
Original comment by petr.ju...@mediamonkey.com
on 17 Sep 2014 at 9:23
New |inspect_element_at| parameter added to CefBrowserHost::ShowDevTools in
trunk revision 1870 and 2171 branch revision 1871.
Original comment by magreenb...@gmail.com
on 11 Oct 2014 at 12:13
Original issue reported on code.google.com by
magreenb...@gmail.com
on 27 Apr 2012 at 5:38