5e45cb0b8d
In v1, clicking a timer notification causes removal of the timer. In v2, clicking a timer notification is a no-op. Previously, an empty action for an Assistant notification was used as a signal to indicate that notification payload should be retrieved from the server. Now, this is only the case for server notifications. An empty action for a client created notification will simply result in a no-op on click. Bug: b:149570650 Change-Id: I48258edb97c891e302e1085f5ed3bc019cfa9340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2238953 Commit-Queue: David Black <dmblack@google.com> Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#777410}
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.