<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to WebKitProtocol</title><link>https://sourceforge.net/p/chromedevtools/wiki/WebKitProtocol/</link><description>Recent changes to WebKitProtocol</description><atom:link href="https://sourceforge.net/p/chromedevtools/wiki/WebKitProtocol/feed" rel="self"/><language>en</language><lastBuildDate>Sat, 25 Apr 2015 13:43:43 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/chromedevtools/wiki/WebKitProtocol/feed" rel="self" type="application/rss+xml"/><item><title>WebKitProtocol modified by Anonymous</title><link>https://sourceforge.net/p/chromedevtools/wiki/WebKitProtocol/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;"WebKit Remote Debugging Protocol" is a Google Chrome/Chromium debug protocol. You will find its description at &lt;a href="http://developers.google.com/chrome-developer-tools/docs/remote-debugging" rel="nofollow"&gt;http://developers.google.com/chrome-developer-tools/docs/remote-debugging&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;This protocol is natively used by in-browser Developer Tools. Historically it succeeds &lt;a class="" href="/p/chromedevtools/wiki/ChromeDevToolsProtocol"&gt;ChromeDevToolsProtocol&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Here its Java client implementation is called &lt;a class="" href="../WIP"&gt;WIP&lt;/a&gt; (in source code and in docs). &lt;/p&gt;
&lt;h3 id="how-to-start-google-chromechromium"&gt;How to start Google Chrome/Chromium&lt;/h3&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;chrome --remote-debugging-port=&amp;lt;port&amp;gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;h3 id="how-to-attach-from-debugger"&gt;How to attach from &lt;a class="" href="../EclipseDebugger"&gt;Debugger&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A launch configuration named "WebKit Protocol" should be created (see &lt;a class="" href="../DebuggerTutorial#Connect"&gt;tutorial&lt;/a&gt;). &lt;/p&gt;
&lt;h3 id="how-to-attach-from-sdk"&gt;How to attach from SDK&lt;/h3&gt;
&lt;p&gt;Use the following create method: &lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;org.chromium.sdk.wip.WipBrowserFactory.INSTANCE.createBrowser(...)
&lt;/pre&gt;&lt;/div&gt;
&lt;h2 id="wip-backends"&gt;WIP Backends&lt;/h2&gt;
&lt;p&gt;Note that the project contains several alternative protocol implementations for the different versions. They are deployed as "WIP Backends" (see &lt;a class="" href="../WipBackends"&gt;main article&lt;/a&gt;). &lt;/p&gt;
&lt;h3 id="protocol-name"&gt;Protocol Name&lt;/h3&gt;
&lt;p&gt;Protocol is called 'WebKit Remote Debuggin Protocol'. You can be sure that you are using this protocol, if you are starting Google Chrome/Chromium with the following parameter: &lt;code&gt;--remote-debugging-port=&amp;lt;port&amp;gt;&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Compare with &lt;a class="" href="../ChromeDevToolsProtocol#Protocol_Name"&gt;ChromeDevTools Protocol&lt;/a&gt;. &lt;/p&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;p&gt;Main page: &lt;a href="http://developers.google.com/chrome-developer-tools/docs/remote-debugging" rel="nofollow"&gt;http://developers.google.com/chrome-developer-tools/docs/remote-debugging&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Blog posts: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="" href="http://blog.chromium.org/2011/05/remote-debugging-with-chrome-developer.html" rel="nofollow"&gt;Remote debugging with Chrome Developer Tools&lt;/a&gt;, The Chromium Blog, May 9th, 2011, &lt;/li&gt;
&lt;li&gt;&lt;a class="" href="http://www.webkit.org/blog/1620/webkit-remote-debugging" rel="nofollow"&gt;WebKit Remote Debugging&lt;/a&gt;, Surfin' Safari, May 9th, 2011. &lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 25 Apr 2015 13:43:43 -0000</pubDate><guid>https://sourceforge.netb89bcbde8d73cdff506e3c0d444c334517295100</guid></item></channel></rss>