18596eb2ce
Recording user actions in a renderer process can't be done using base::RecordAction and friends because there is no running metrics service. Instead, there's a call in the content layer, which passes the actions across an IPC bridge, so the actions can be recorded in the browser process. Since the call is in the content layer, inject a dependency using the Client interface. Fixed: 1231356 Change-Id: I6e6cc5d2f652c9f8b930ce5d9355284028b8be1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3043668 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#905385}
Chrome
This directory contains the open source, application layer of Google Chrome.
Unlike other parts of Chromium like //content, which provide framework intended to support multiple products, this directory contains code that is focused on building specific products with opinionated UX.
Specific products include:
- Chrome desktop browser for Chrome OS, Windows, Mac and Linux
- Chrome mobile browser for Android
- Chrome OS system UI
See //ios/chrome for the Chrome mobile browser for iOS, and note that code that is shared between //chrome and //ios/chrome is typically factored out into //components.