summaryrefslogtreecommitdiffstats
path: root/content/public/browser/devtools_manager.h
Commit message (Collapse)AuthorAgeFilesLines
* TabContents -> WebContentsImpl, part 8.avi@chromium.org2012-04-131-2/+3
| | | | | | | | | | | | "Detab" content/browser/debugger. BUG=105875 TEST=no change Review URL: http://codereview.chromium.org/10065017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132193 0039d316-1c4b-4281-b951-d872f2087c98
* TabContents -> WebContentsImpl, part 1.avi@chromium.org2012-04-101-2/+0
| | | | | | | | | | BUG=105875 TEST=no change Review URL: http://codereview.chromium.org/10024034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131571 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: provide a way for browser process to log into the renderer's tools ↵pfeldman@chromium.org2012-03-121-1/+8
| | | | | | | | | | | console. BUG=116769 Review URL: http://codereview.chromium.org/9663051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126164 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: look up client hosts for the given tab contents while navigating.pfeldman@chromium.org2012-01-201-0/+4
| | | | | | | | BUG=110613 Review URL: https://chromiumcodereview.appspot.com/9226016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@118448 0039d316-1c4b-4281-b951-d872f2087c98
* Get rid of a bunch of tab_contents.h includes from chrome. These are all ↵jam@chromium.org2012-01-041-1/+1
| | | | | | | | | trivial changes to use WebContents instead of TabContents. BUG=98716 Review URL: http://codereview.chromium.org/9030032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116392 0039d316-1c4b-4281-b951-d872f2087c98
* Define DevTools content APIyurys@chromium.org2011-12-011-0/+79
The API consists of the following parts: * DevToolsManager routes messages between devtools agents and clients * DevToolsAgentHost provides an abstract interface to the debuggee, currently it is either RenderViewHost or Shared Worker. Client can obtain DevToolsAgentHost from DevToolsAgentHostRegistry. * DevToolsClientHost is an API that should be implemented by DevTools front-end. There is a default Chromium implementation living in chrome/ and a remote debugging server which also implements this interface. Clients can extend it in order to provide custom front-end. There is a default DevTools front-end implementation and content/ provides a way for creating corresponding DevToolsClientHost by means of DevToolsClientHost::CreateDevToolsFrontendHost. The embedder just needs to provide a concrete delegate. * This patch also removes DevToolsHost_ForwardToAgent and DevToolsHost_ForwardToClient IPC messages which were used to forward only one message. DevTools IPC messages are now hidden behind the devtools content API. BUG=104625 TEST=Existing tests Review URL: http://codereview.chromium.org/8549022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112473 0039d316-1c4b-4281-b951-d872f2087c98