bff7ae96a7
When Wi-Fi sync is first enabled and a list of synced networks has to be merged with the local networks on a device, use the last connected timestamp to decide which configuration should be used. Bug: 966270 Change-Id: Id7688a0fdb9e7922cee8ffec0ef69b804436e3e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093274 Reviewed-by: James Vecore <vecore@google.com> Commit-Queue: Jon Mann <jonmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#750257}
Chrome OS
This directory contains low-level support for Chrome running on Chrome OS. Many subdirectories contain Chrome-style C++ wrappers around operating system components.
For example, //chromeos/dbus contains wrappers around the D-Bus interfaces to system daemons like the network configuration manager (shill). Most other directories contain low-level utility code. For example, //chromeos/disks has utilities for mounting and unmounting disk volumes.
There are two exceptions:
-
//chromeos/services contains mojo services that were not considered sufficiently general to live in top-level //services. For example //chromeos/services/secure_channel bootstraps a secure communications channel to an Android phone over Bluetooth, enabling multi-device features like instant tethering.
-
//chromeos/components contains C++ components that were not considered sufficiently general to live in top-level //components. For example, //chromeos/components/account_manager manages the user's GAIA accounts, but is used as the backend for UI that only exists on Chrome OS devices.
Note, //chromeos does not contain any user-facing UI code, and hence it has "-ui" in its DEPS. The contents of //chromeos should also not depend on //chrome or //content.