https://sourceforge.net/p/chromedevtools/wiki/WipBackendDevelopment/Recent changes to WipBackendDevelopmentenSat, 25 Apr 2015 13:43:40 -0000https://sourceforge.net/p/chromedevtools/wiki/WipBackendDevelopment/<div class="markdown_content"><p>This is an article about <a class="" href="../WIP">WIP</a> support development. </p> <h2 id="development-process">Development process</h2> <p>As WebKit Remote Debugging Protocol keeps evolving and different versions of Chromium should be supported, client implementation is forked into several <a class="" href="../WipBackends">WipBackends</a>. </p> <p>See also <a class="" href="../DesignOverview">DesignOverview</a>. </p> <h3 id="changes-from-v8-native-protocol">Changes from V8 native protocol</h3> <p>SDK is meant to provide a uniform interface to all existing or future protocols. However some small differences in behavior or features are possible. This is a preview of the list of WIP implementation differences. </p> <ul> <li>JavaScript VM is not necessarily V8. Theoretically, other JavaScript engine could be used in debuggee. This may affect the feature-set. E.g. live editing might be disabled. </li> <li>No "ref-id" property for values. Ref-id can be used to visually distinguish two objects with similar properties. This may be not available on WIP back-end. </li> <li>Permanent values, that outlive DebugContext (i.e. a single paused state). </li> <li>Additional protocol domains might be supported in the future, including access to DOM tree with CSS. </li> </ul></div>AnonymousSat, 25 Apr 2015 13:43:40 -0000https://sourceforge.net362c1521eb314442bbef3c1cfa2e94b2833aea4d