Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 | 1 year ago | |
---|---|---|
.. | ||
arc | 1 year ago | |
device_activity | 1 year ago | |
disks | 1 year ago | |
drivefs | 1 year ago | |
enhanced_network_tts | 1 year ago | |
fwupd | 1 year ago | |
geolocation | 1 year ago | |
hid_detection | 1 year ago | |
login | 1 year ago | |
multidevice | 1 year ago | |
peripheral_notification | 1 year ago | |
phonehub | 1 year ago | |
policy | 1 year ago | |
power | 1 year ago | |
proximity_auth | 1 year ago | |
settings | 1 year ago | |
smbfs | 1 year ago | |
test | 1 year ago | |
tether | 1 year ago | |
timezone | 1 year ago | |
tpm | 1 year ago | |
trial_group | 1 year ago | |
BUILD.gn | 1 year ago | |
DEPS | 1 year ago | |
OWNERS | 1 year ago | |
README.md | 1 year ago |
DEPRECATED. If you’re about adding new component for ash-chrome only, consider using //chromeos/ash/components.
This directory contains components that are used by //ash system UI and window manager code. It sits «below» //ash in the dependency graph. For C++ code, think of //ash/components like top-level //components, but for code that is only used on ChromeOS, and only for system UI / window manager support.
Some subdirectories contain low-level utility code. For example, //ash/components/disks has utilities for mounting and unmounting disk volumes.
Much of this code used to live in //chromeos/components. The Lacros project is extracting browser functionality into a separate binary. As part of this migration, code used only by the ash-chrome system UI binary moved into «ash» directories. See the Chrome OS source directory migration design doc for details.