
Notable changes: . Use the regular aura-path for setting the LocalSurfaceId for the compositor, instead of specially setting it from WindowTreeClient, when the window-server sets the LocalSurfaceId with a bounds-change. WindowTreeHost::SetBoundsInPixels() is changed to take LocalSurfaceId as an input-param to facilitate this. . When the client itself changes the size, do not set the LocalSurfaceId on the compositor multiple times for the same size from various places (e.g. WindowTreeHostMus, WindowTreeClient etc.). . Add validation checks for ui::Compositor that a new LocalSurfaceId is assigned whenever the size changes. This makes it easier to catch errors earlier in the pipeline. BUG=821987 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Ic9703c57b7a7f9ef2b65b34fa38c8ec7de9e9f36 Reviewed-on: https://chromium-review.googlesource.com/1014568 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#551588}
Headless Chromium
Headless Chromium allows running Chromium in a headless/server environment. Expected use cases include loading web pages, extracting metadata (e.g., the DOM) and generating bitmaps from page contents -- using all the modern web platform features provided by Chromium and Blink.
There are two ways to use Headless Chromium:
Usage via the DevTools remote debugging protocol
- Start a normal Chrome binary with the
--headless
command line flag (Linux-only for now):
$ chrome --headless --remote-debugging-port=9222 https://chromium.org
Currently you'll also need to use --disable-gpu
to avoid an error from a
missing Mesa library.
- Navigate to
http://localhost:9222
in another browser to open the DevTools interface or use a tool such as Selenium to drive the headless browser.
Usage from Node.js
For example, the chrome-remote-interface Node.js package can be used to extract a page's DOM like this:
const CDP = require('chrome-remote-interface');
CDP((client) => {
// Extract used DevTools domains.
const {Page, Runtime} = client;
// Enable events on domains we are interested in.
Promise.all([
Page.enable()
]).then(() => {
return Page.navigate({url: 'https://example.com'});
});
// Evaluate outerHTML after page has loaded.
Page.loadEventFired(() => {
Runtime.evaluate({expression: 'document.body.outerHTML'}).then((result) => {
console.log(result.result.value);
client.close();
});
});
}).on('error', (err) => {
console.error('Cannot connect to browser:', err);
});
Usage as a C++ library
Headless Chromium can be built as a library for embedding into a C++ application. This approach is otherwise similar to controlling the browser over a DevTools connection, but it provides more customization points, e.g., for networking and mojo services.
Headless Example is a small sample application which demonstrates the use of the headless C++ API. It loads a web page and outputs the resulting DOM. To run it, first initialize a headless build configuration:
$ mkdir -p out/Debug
$ echo 'import("//build/args/headless.gn")' > out/Debug/args.gn
$ gn gen out/Debug
Then build the example:
$ ninja -C out/Debug headless_example
After the build completes, the example can be run with the following command:
$ out/Debug/headless_example https://www.google.com
Headless Shell is a more capable headless application. For instance, it supports remote debugging with the DevTools protocol. To do this, start the application with an argument specifying the debugging port:
$ ninja -C out/Debug headless_shell
$ out/Debug/headless_shell --remote-debugging-port=9222 https://youtube.com
Then navigate to http://localhost:9222
with your browser.
Embedder API
The embedder API allows developers to integrate the headless library into their application. The API provides default implementations for low level adaptation points such as networking and the run loop.
The main embedder API classes are:
HeadlessBrowser::Options::Builder
- Defines the embedding options, e.g.:SetMessagePump
- Replaces the default base message pump. Seebase::MessagePump
.SetProxyServer
- Configures an HTTP/HTTPS proxy server to be used for accessing the network.
Client/DevTools API
The headless client API is used to drive the browser and interact with loaded web pages. Its main classes are:
HeadlessBrowser
- Represents the global headless browser instance.HeadlessWebContents
- Represents a single "tab" within the browser.HeadlessDevToolsClient
- Provides a C++ interface for inspecting and controlling a tab. The API functions corresponds to DevTools commands. See the client API documentation for more information.
Resources and Documentation
Mailing list: headless-dev@chromium.org
Bug tracker: Internals>Headless
File a new bug (bit.ly/2pP6SBb)
- Runtime headless mode on Windows OS
- BeginFrame sequence numbers + acknowledgements
- Deterministic page loading for Blink
- Crash dumps for Headless Chrome
- Runtime headless mode for Chrome
- Virtual Time in Blink
- Headless Chrome architecture
- Headless Chrome C++ DevTools API
- Session isolation in Headless Chrome
- Headless Chrome mojo service
- Controlling BeginFrame through DevTools
- Viewport bounds and scale for screenshots
- BlinkOn 6 presentation slides
- Architecture design doc