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}
//pdf contains the PDF plugin, its Blink-based replacement, as well as PDF
utility functions that leverage PDFium. It can use low-level components that
live below the content layer, as well as other foundational code like
//printing. It should not use //content or anything in //components that
lives above the content layer. Code that lives above the content layer should
live in //components/pdf, or in the embedder. All the code here should run in
sandboxed child processes.
TODO(crbug.com/1220865): Remove existing //content dependencies.