Chrome supports a single process mode [1], and has in-process APIs [2] for manipulating the DOM via C++. I would be surprised if it wasn't already possible to

Chrome supports a single process mode [1], and has in-process APIs [2] for manipulating the DOM via C++. I would be surprised if it wasn't already possible to make use of these from the embedder side if you're in single-process mode. But if it's not, I wouldn't expect there to be pushback on changes to that effect. [1] https://code.google.com/p/chromium/codesearch#chromium/src/content/public/common/content_switches.cc&sq=package:chromium&l=746 https://code.google.com/p/chromium/codesearch#chromium/src/c... [2] https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/public/web/WebElement.h&sq=package:chromium https://code.google.com/p/chromium/codesearch#chromium/src/t...