
It is not possible for elements to know if the lang attribute has changed for one of its ancestors. This change propagates lang attribute updates down the tree. The Permission Element listens to this change and updates the text accordingly. Bug: 374677445 Change-Id: Ic41c90a13f3fbb1faecc8298993bc74cb185137e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003767 Auto-Submit: Ravjit Uppal <ravjit@chromium.org> Reviewed-by: Peter Kvitek <kvitekp@chromium.org> Commit-Queue: Peter Kvitek <kvitekp@chromium.org> Reviewed-by: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1391078}
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.
As of M118, precompiled headless_shell
binaries are available for download
under the name chrome-headless-shell
via Chrome for Testing
infrastructure.
There are two ways to use Headless Chromium:
Usage via the DevTools remote debugging protocol
- Start a normal Chrome binary with the
--headless=old
command line flag:
$ chrome --headless=old --remote-debugging-port=9222 https://chromium.org/
- Navigate to
chrome://inspect/
in another instance of Chrome.
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');
(async () => {
let client;
try {
// Connect to browser
client = await CDP();
// Extract used DevTools domains.
const {Page, Runtime} = client;
// Enable events on domains we are interested in.
await Page.enable();
await Page.navigate({url: 'https://example.com'});
await Page.loadEventFired();
// Evaluate outerHTML after page has loaded.
const expression = {expression: 'document.body.outerHTML'};
const { result } = await Runtime.evaluate(expression);
console.log(result.value);
} catch (err) {
console.error('Cannot connect to browser:', err);
} finally {
if (client) {
await client.close();
}
}
})();
Alternatvely, the Puppeteer Node.js package can be used to communicate with headless, for example:
import puppeteer from 'puppeteer';
(async () => {
const browser = await puppeteer.launch({headless: 'shell'});
const page = await browser.newPage();
await page.goto('https://example.com');
const title = await page.evaluate(() => document.title);
console.log(title);
await browser.close();
})();
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 (Design Doc)
- Session isolation in Headless Chrome
- Headless Chrome mojo service
- Controlling BeginFrame through DevTools
- Viewport bounds and scale for screenshots
- BlinkOn 6 presentation slides