The Chromium application uses different types, coding styles, and code layout than the third-party WebKit code. The WebKit "glue" provides a more convenient embedding API for WebKit using Google coding conventions and types (for example, we use std::string instead of WebCore::String and GURL instead of KURL). WebChromium keeps track of the full frame tree for each tab in the browser process. WebContents hosts a tree of FrameTreeNode objects, mirroring the frame tree of the current page. Each FrameTreeNode contains frame-specific information (e.g., the frame's name, origin, etc).
content/public/browser/web_contents.h - chromium/src - Git at …
WebSince a frame is only uniquely identified within a renderer process, and a WebContents can be a delegate for several RenderViewHosts in different renderer processes, we need the … WebThe “content” module is located in src/content, and is the core code needed to render a page using a multi-process sandboxed browser. It includes all the web platform features … devonshire white plains
Content module - Google Open Source
WebwebContents.fromDevToolsTargetId (targetId) targetId string - The Chrome DevTools Protocol TargetID associated with the WebContents instance. Returns WebContents … WebHigh-level overview. The “content” module is located in src/content, and is the core code needed to render a page using a multi-process sandboxed browser. It includes all the web platform features (i.e. HTML5) and GPU acceleration. It does not include Chrome features, e.g. extensions/autofill/spelling etc. Web// Used to specify that the new WebContents creation is driven by the // renderer process. In this case, the renderer-side objects, such as // RenderFrame, have already been created on the renderer side, and // WebContents construction should take this into account. bool renderer_initiated_creation; devonshire west palm